Forum Discussion
KingsleyU
Sep 11, 2024Brass Contributor
Connect-Aipservice is not working
Hello everyone,
Please is anyone able to connect to the aip service using powershell version 5.5 and above?
Even after installing and importing the aip service module, the connect-aipservice failed to work with all its parameters.
However, creating and publishing sensitivity label policy is working.
Thanks.
Can confirm the follow steps:
Install-Module -Name AzureInformationProtection
Import-Module -Name AzureInformationProtection
$PSVersionTable.PSVersion (version 5.1 or later)
Connect-AipService -Credential (Get-Credential)
- KingsleyUBrass Contributor
- KingsleyUBrass ContributorMoreover, I got more information about deprecated modules as below:
Deprecated modules
The AzureInformationProtection and AADRM modules are now deprecated and was replaced with newer modules. The newer modules provide the same functionality with renamed cmdlets.
The renamed cmdlets in the current modules have aliases to the old cmdlets. Cmdlets from the old modules that were already deprecated and no longer used weren't carried forward to the newer modules.
The AzureInformationProtection module was replaced with the PurviewInformationProtection module. Support for this older module ended May 13, 2024.
The AADRM module was replaced with the AIPService module. Support for this older module ended July 15, 2020.
https://learn.microsoft.com/en-us/powershell/azure/aip/overview?view=azureipps#purviewinformationprotection
- Works fine here. Do note that the module is only supported on Windows PowerShell (so NO PowerShell 7+). Some other common issues are detailed here: https://learn.microsoft.com/en-us/troubleshoot/azure/entra/entra-id/user-prov-sync/fail-connect-azure-information-protection-powershell
- KingsleyUBrass ContributorWill be checking affected tenant again then revert. Obviously PS version was above 7.0 but even without providing a credential, the same error message that "...wrong username and password combination..." was displayed. Typically, running Connect-Aipservice should popup the credential dialog but failed.
Thanks.