Merge pull request #245257 from ManoharLakkoju-MSFT/patch-58

(AzureCXP) fixes MicrosoftDocs/azure-docs#112269

Author: prmerger-automator[bot]

articles/active-directory/app-provisioning/inbound-provisioning-api-faqs.md

@@ -48,7 +48,7 @@ Yes, the provisioning API supports on-premises AD domains as a target.
 
 ## How do we get the /bulkUpload API endpoint for our provisioning app?
 
-The /bulkUpload API is available only for apps of the type: "API-driven inbound provisioning to Azure AD" and "API-driven inbound provisioning to on-premises Active Directory". You can retrieve the unique API endpoint for each provisioning app from the Provisioning blade home page.  In **Statistics to date** > **View technical information** and copy the **Provisioning API Endpoint** URL. It has the format:
+The /bulkUpload API is available only for apps of the type: "API-driven inbound provisioning to Azure AD" and "API-driven inbound provisioning to on-premises Active Directory". You can retrieve the unique API endpoint for each provisioning app from the Provisioning blade home page.  In **Statistics to date** > **View technical information**,copy the **Provisioning API Endpoint** URL. It has the format:
 
 ```http
 https://graph.microsoft.com/beta/servicePrincipals/{servicePrincipalId}/synchronization/jobs/{jobId}/bulkUpload
@@ -184,4 +184,4 @@ The current API only supports inbound data. Here are some options to consider fo
 ## Next steps
 
 - [Configure API-driven inbound provisioning app](inbound-provisioning-api-configure-app.md)
-- To learn more about API-driven inbound provisioning, see [inbound user provisioning API concepts](inbound-provisioning-api-concepts.md).
+- To learn more about API-driven inbound provisioning, see [inbound user provisioning API concepts](inbound-provisioning-api-concepts.md).