Do you need to use PowerShell to administer the protection service from Azure Information Protection? You might not need to if all your configuration can be done in the Azure portal or the Microsoft Purview compliance portal. However, you need to use PowerShell for some advanced configurations and you might also prefer to use PowerShell for more efficient command-line control and scripting.
The table in the next section includes some of the advanced configuration scenarios that use PowerShell. When the configuration can also be completed without using PowerShell, this information is also included in the table.
For a complete list of the available cmdlets for this module, with more information about each one, see AIPService.
In addition to this service-side PowerShell module, the Azure Information Protection client installs a supplemental PowerShell module, AzureInformationProtection.
This client module supports classifying and protecting multiple files so that, for example, you can bulk-protect all files in a folder. For more information, see Using PowerShell with the Azure Information Protection client from the admin guide.
Cmdlets grouped by administration task
If you need to…
…use the following cmdlets
Migrate from on-premises Rights Management (AD RMS or Windows RMS) to Azure Information Protection.
Configure the maximum number of days that content that your organization protects can be accessed without an internet connection (the use license validity period).
This learning path covers cmdlets that are commonly used for system administration tasks related to Active Directory, network configuration, server administration, and Windows 10 device administration.
Describes an issue in which you can't connect to the Azure Information Protection service by using Windows PowerShell in Office 365. Provides a resolution.