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...
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)
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?
- I don't think so.. Don't know what the limitations, if any, are using a MSDN subscription...
- I’m going to open a case with Microsoft. I’ll update when resolved.