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...
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?
- Ok, no experience in that and your connecting account has enough permissions?
- Assigned roles in Azure AD are Attack Simulator admin, Compliance Admin, Compliance Data Admin, Conditional Access Admin and Global Admin. In the Compliance/Security portal, I have Organizational Management and Insider Risk Management role groups assigned. Is there something I'm, missing?
