Error Workplace provisioning with azure active directory does not integrate properly

Question

Hello everyone ,I have a problem when configuring the automatic provisioning with azure following the corresponding documentation I put correctly the url of tenant "https://scim.workplace.com/" and then to authorization in azure , I get an additional window redirecting to workplace to add "Azure AD scim provisioning " I click on add and I get another window saying "Try again using another browser.
We were unable to connect to that service, probably due to the configuration set by your IT team. Open Azure in a different web browser to try again".

despite having the system administrator role and changing browser and clearing the cache does not allow me to properly configure the workplace integration. Is there any additional permissions or steps to take? Greetings.

Answer 1

@Cesart

Thank you for reaching out to us. By looking at the error message seems the account doesnt have enough permissions to authorize.

To configure provisioning ( user account in Azure AD ) should be application administrator, cloud application administrator, application owner or Global Administrator, can you re-visit the permissions of the account being used ?

Also ensure your workplace by Facebook account has admin permissions ?

Reference article: https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/workplace-by-facebook-provisioning-tutorial#update-a-workplace-by-facebook-application-to-use-the-workplace-by-facebook-scim-20-endpoint

Let me know if you have any further questions.

Answer 2

Did you ever get this resolved @Cesart

Answer 3

I have the same problem, gave the user all the necessary rights in Azure AD and it´s admin in Workplace.
Still get the same error.

Try that again using a different browser
We couldn't connect to that service, likely because of settings put in place by your IT team. Open Azure in a different Web browser to try again.

Answer 4

I'm having the same error on Multiple workplace instance using different Azure tenants. Did anyone get this resolved?

Answer 5

We have also experienced the same issue.
The process of setting up the provisioning is very intermittent. It took about 10 attempts to work.

Let’s hope they improve soon.