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 s...
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?
Harm_Veenstra I'm using a tenant that I received via an MSDN subscription to test out information barriers to better understand them for our production tenant. I get the same message, and it appears that 'New-InformationBarrierPolicy' isn't loaded when connecting to the Security and Compliance Powershell. (Not OP, but ok)
- And MSDN = CDX in your case?
