Forum Discussion

Little_Joe's avatar
Little_Joe
Bronze Contributor
Sep 25, 2021

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...
AzureAD PowerShell Module
ExchangeOnline PowerShell Module
catch_mike's avatar
catch_mike
Copper Contributor
Jun 08, 2022
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.
catch_mike's avatar
catch_mike
Copper Contributor
Jun 08, 2022

catch_mike 

 

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's avatar
    AgeorgeMSFT
    Icon for Microsoft rankMicrosoft
    Mar 23, 2023
    Is this confirmed? the M365 E5 Developer license cannot be used for testing Information Barriers?
    • xctpro's avatar
      xctpro
      Copper Contributor
      Oct 12, 2023

      Yes !AgeorgeMSFT 

      No money no test.

      • RaSoRe's avatar
        RaSoRe
        Copper Contributor
        Jan 14, 2024
        Thanks for your information. It has helped me a lot, I was already going crazy. Same behaviour from my developer tenant.

Resources