Forum Discussion
The term 'New-informationbarrierPolicy' is not recognized as the name of a cmdlet, function
Hello guys,
Does any one can run the "New-InformationBarrierPolicy" cmdlets successfully with EXO V2 module?
I've login successful and granted permission with Information Barrier Processor but still cannot run it..
From the error message seems no such cmdlets...
- Did you resolve this issue i_ride_ostriches? I also have an MSDN subscription and get the same error when running New-InformationBarrierPolicy cmdlet with EXO v2 modules. If I connect to other production tenants, I *can* see the cmdlet.
Also, in https://compliance.microsoft.com Purview compliance portal > Information barriers, the tenant connected to MSDN only has Segments; and fails when running commands.
In another production tenant it has Segments, Policies and Policy applications. I wonder if that is the same underlying issue.
- AgeorgeMSFT
Microsoft
Is this confirmed? the M365 E5 Developer license cannot be used for testing Information Barriers?
You will have to connect to the Security & Compliance Center to run the command (https://docs.microsoft.com/en-us/powershell/exchange/connect-to-scc-powershell?view=exchange-ps). Command would be :
Connect-IPPSSession -UserPrincipalName admin @ domainname.onmicrosoft.comAfterwards the New-InformationBarrierPolicy cmdlet should be available if you have enough permissions
- Well tried before... This seems only work with certain subscription except the Developer one.
- The developer one?
- Did this solve your issue?
