HaloCRM Guides

Guides > Microsoft CSP Issue after changes from DAP to GDAP

Microsoft CSP Issue after changes from DAP to GDAP

This is a temporary workaround for users on versions before v2.108.1.

1. Go to the Azure Application page for the CSP application and remove the user_impersonation permission from the application and Save.

2. The below URL needs to be populated with the Azure Application Client ID and also the Tenant ID for the Customer in CSP (see image below for examples of this)

https://login.microsoftonline.com/{CUSTOMER_TENANT_ID}/adminconsent?client_id={APPLICATION_CLIENT_ID}

3. Click this link once populated and authenticate the login. At this point, you may get a '404' Halo page:

Don't worry about this - the permissions should have updated correctly.

4. Delete the tenant mapping from the CSP configuration & re-import. This will ensure the tenant is imported with the most recent permissions.

5. Go to the Azure Application page for the CSP application and add the user_impersonation permission back into the application and Save.

If you have mapped all of the Customers/Tenants into HaloPSA but need to generate the link to satisfy the GDAP requirement we have a report available in the Online Repository called "GDAP Admin Consent" that can list the URLs you need to use.