Forum Discussion
Little_Joe
Sep 25, 2021Bronze Contributor
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...
catch_mike
Jun 08, 2022Copper Contributor
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
Mar 23, 2023Is this confirmed? the M365 E5 Developer license cannot be used for testing Information Barriers?
- xctproOct 12, 2023Copper Contributor
Yes !AgeorgeMSFT
No money no test.
- RaSoReJan 14, 2024Copper ContributorThanks for your information. It has helped me a lot, I was already going crazy. Same behaviour from my developer tenant.