You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -968,7 +968,7 @@ The SCIM endpoint must have an HTTP address and server authentication certificat
968
968
* WoSign
969
969
* DST Root CAX3
970
970
971
-
The .NET Core SDK includes an HTTPS development certificate that can be used duringdevelopment, thecertificateisinstalledaspartofthefirst-runexperience. DependingonhowyouruntheASP.NETCoreWebApplicationitwilllistentoadifferentport:
971
+
The .NET Core SDK includes an HTTPS development certificate that is used during development. The certificate is installed as part of the first-run experience. Depending on how you run the ASP.NET Core Web Application it listens to a different port:
@@ -1351,10 +1351,10 @@ Once the initial cycle has started, you can select **Provisioning logs** in the
1351
1351
1352
1352
## Publish your application to the Azure AD application gallery
1353
1353
1354
-
Ifyou'rebuildinganapplicationthatwillbeusedbymorethanonetenant, youcanmakeitavailableintheAzureADapplicationgallery. It's easy for organizations to discover the application and configure provisioning. Publishing your app in the Azure AD gallery and making provisioning available to others is easy. Check out the steps [here](../manage-apps/v2-howto-app-gallery-listing.md). Microsoft will work with you to integrate your application into our gallery, test your endpoint, and release onboarding [documentation](../saas-apps/tutorial-list.md) for customers to use.
1354
+
Ifyou'rebuildinganapplicationusedbymorethanonetenant, makeitavailableintheAzureADapplicationgallery. It's easy for organizations to discover the application and configure provisioning. Publishing your app in the Azure AD gallery and making provisioning available to others is easy. Check out the steps [here](../manage-apps/v2-howto-app-gallery-listing.md). Microsoft works with you to integrate your application into the gallery, test your endpoint, and release onboarding [documentation](../saas-apps/tutorial-list.md) for customers.
Usethechecklisttoonboardyourapplicationquicklyandcustomershaveasmoothdeploymentexperience. Theinformationisgatheredfromyou when onboarding to the gallery.
@@ -1418,7 +1418,7 @@ Best practices (recommended, but not required):
1418
1418
> [!NOTE]
1419
1419
>Whileit's not possible to setup OAuth on the non-gallery applications, you can manually generate an access token from your authorization server and input it as the secret token to a non-gallery application. This allows you to verify compatibility of your SCIM server with the Azure AD Provisioning Service before onboarding to the app gallery, which does support the OAuth code grant.
1420
1420
1421
-
**Long-livedOAuthbearertokens:**Ifyourapplicationdoesn't support the OAuth authorization code grant flow, instead generate a long lived OAuth bearer token that an administrator can use to set up the provisioning integration. The token should be perpetual, or else the provisioning job will be [quarantined](application-provisioning-quarantine-status.md) when the token expires.
1421
+
**Long-livedOAuthbearertokens:**Ifyourapplicationdoesn't support the OAuth authorization code grant flow, instead generate a long lived OAuth bearer token that an administrator can use to set up the provisioning integration. The token should be perpetual, or else the provisioning job is [quarantined](application-provisioning-quarantine-status.md) when the token expires.
0 commit comments