Skip to content

Commit 6c58b46

Browse files
Update workplacebyfacebook-provisioning-tutorial.md
1 parent a3d9eed commit 6c58b46

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

articles/active-directory/saas-apps/workplacebyfacebook-provisioning-tutorial.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,19 +24,21 @@ ms.collection: M365-identity-device-management
2424
This tutorial describes the steps you need to perform in both Workplace by Facebook and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Workplace by Facebook](https://work.workplace.com/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../manage-apps/user-provisioning.md).
2525

2626
## Migrating to the new Workplace by Facebook application
27+
If you have an existing integration with Workplace by Facebook, please see the below section about changes coming. If you are setting up Workplace by Facebook for the first time you can skip this section and move to the capabilities supported.
28+
2729
#### What's changing?
2830
* Changes on the Azure AD side: The authorization method to provision users in Workplace has historically been a long lived secret token. Soon you will see the authorization method changed to the OAuth authorization grant.
29-
* Changes on the Workplace side: Previously the Azure AD app was a custom integration in the Workplace. Now you will see Azure AD in the Workplace integrations directory as a third party application.
31+
* Changes on the Workplace side: Previously the Azure AD app was a custom integration in Workplace by Facebook. Now you will see Azure AD in the Workplace integrations directory as a third party application.
3032

3133

3234

3335
#### What do I need to do to migrate my existing custom integration to the new application?
3436
If you have an existing Workplace integration with a valid token, **no action is required**. We are automatically migrating customers each week to the new application. This is done completely behind the scenes. If you can't wait and want to move to the new application manually, you can add a new instance of Workplace from the gallery, and configure provisioning again. All new instances of Workplace will automatically be using the new application version.
3537

3638

37-
If your Workplace integration is in quarantine, you will need to supply a valid token again in order for us to migrate you. The admin credentials section will be greyed out, but you can append the following to your URL to save credentials again.
39+
If your Workplace integration is in quarantine, you will need to supply a valid token again in order for us to migrate you. The admin credentials section will be greyed out, but you can append the following (**?Microsoft_AAD_IAM_userProvisioningEnableCredentialsOverride=true**) to your URL to save credentials again.
3840

39-
https://portal.azure.com/**?Microsoft_AAD_IAM_userProvisioningEnableCredentialsOverride=true**
41+
https://portal.azure.com/?Microsoft_AAD_IAM_userProvisioningEnableCredentialsOverride=true
4042

4143

4244
#### The admin credentials section is greyed out on my application and I can't save. Why?

0 commit comments

Comments
 (0)