How to update AzureCP

Start a new PowerShell console to ensure the use of up to date persisted objects, which avoids concurrency update errors.
Assemblies must be updated manually on SharePoint servers that do not run SharePoint service “Microsoft SharePoint Foundation Web Application”.
If something goes wrong, check this page to fix issues.

  • Run Update-SPSolution on the server running central administration:
# This will start a timer job that will deploy the update on SharePoint servers. Central administration will restart during the process
Update-SPSolution -GACDeployment -Identity "AzureCP.wsp" -LiteralPath "F:\Data\Dev\AzureCP.wsp"
  • Visit central administration > System Settings > Manage farm solutions: Wait until solution status shows “Deployed”

    If status shows “Error”, restart the SharePoint timer service on servers where depployment failed, start a new PowerShell process and run Update-SPSolution again.

  • Update assembly manually on SharePoint servers that do not run the service “Microsoft SharePoint Foundation Web Application”
  • Restart IIS service and SharePoint timer service on each SharePoint server
  • Visit central administration > Security > AzureCP global configuration page: Review the configuration

Breaking changes with previous versions

Some versions have breaking changes and some settings will be reset to their default values during the upgrade:

  • Upgrade to v12:
    • Claim type configuration list will be reset. This is due to the complete rewriting of this list.
    • Groups permissions are now created using the Id instead of the DisplayName. See below for more information.
  • Upgrade to v13: Claim type configuration list will be reset. This is due to the changes made to handle Guest users.

Group identifier changes

Starting with v12, AzureCP creates group entities (permissions) using the Id instead of the DisplayName. There are 2 reasons for this change:

  • Group Id is unique, DisplayName is not
  • With group Id, AzureCP can get nested group membership of users during augmentation, which is not possible with the DisplayName

As a consequence of this change, permissions granted to Azure AD groups before v12 will stop working, because the group value in the SAML token of AAD users (set with the Id) won’t match the group value of group permission in the sites (set with the DisplayName).

To fix this, group permissions must be migrated to change their value with the Id. This can be done by calling method SPFarm.MigrateGroup() for each group to migrate:

# SPFarm.MigrateGroup() will migrate group "c:0-.t|contoso.local|AzureGroupDisplayName" to "c:0-.t|contoso.local|a5e76528-a305-4345-8481-af345ea56032" in the whole farm
$oldlogin = "c:0-.t|contoso.local|AzureGroupDisplayName";
$newlogin = "c:0-.t|contoso.local|a5e76528-a305-4345-8481-af345ea56032";
[Microsoft.SharePoint.Administration.SPFarm]::Local.MigrateGroup($oldlogin, $newlogin);

Important: This operation is farm wide and must be tested carefully before it is applied in production environments.

Alternatively, administrators can configure AzureCP to use the property DisplayName for the groups, instead of the Id:

Add-Type -AssemblyName "AzureCP, Version=, Culture=neutral, PublicKeyToken=65dc6b5903b51636"
$config = [azurecp.AzureCPConfig]::GetConfiguration("AzureCPConfig")
# Get the ClaimTypeConfig used for groups and set property DirectoryObjectProperty to DisplayName
$ctConfig = $config.ClaimTypes| ?{$_.ClaimType -eq ""}
$ctConfig.DirectoryObjectProperty = [azurecp.AzureADObjectProperty]::DisplayName