Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into upd

Author: greg-lindsay

articles/active-directory/app-provisioning/user-provisioning.md

@@ -7,7 +7,7 @@ ms.service: active-directory
 ms.subservice: app-provisioning
 ms.topic: overview
 ms.workload: identity
-ms.date: 02/09/2023
+ms.date: 02/14/2023
 ms.author: kenwith
 ms.reviewer: arvinh
 ---
@@ -20,7 +20,7 @@ In Azure Active Directory (Azure AD), the term *app provisioning* refers to auto
 
 Azure AD application provisioning refers to automatically creating user identities and roles in the applications that users need access to. In addition to creating user identities, automatic provisioning includes the maintenance and removal of user identities as status or roles change. Common scenarios include provisioning an Azure AD user into SaaS applications like [Dropbox](../../active-directory/saas-apps/dropboxforbusiness-provisioning-tutorial.md), [Salesforce](../../active-directory/saas-apps/salesforce-provisioning-tutorial.md), [ServiceNow](../../active-directory/saas-apps/servicenow-provisioning-tutorial.md), and many more.
 
-Azure AD also supports provisioning users into applications hosted on-premises or in a virtual machine, without having to open up any firewalls. If your application supports [SCIM](https://aka.ms/scimoverview), or you've built a SCIM gateway to connect to your legacy application, you can use the Azure AD Provisioning agent to [directly connect](./on-premises-scim-provisioning.md) with your application and automate provisioning and deprovisioning. If you have legacy applications that don't support SCIM and rely on an [LDAP](./on-premises-ldap-connector-configure.md) user store or a [SQL](./tutorial-ecma-sql-connector.md) database, Azure AD can support those as well. 
+Azure AD also supports provisioning users into applications hosted on-premises or in a virtual machine, without having to open up any firewalls. Your application must support [SCIM](https://aka.ms/scimoverview). Or, you must build a SCIM gateway to connect to your legacy application. If so, you can use the Azure AD Provisioning agent to [directly connect](./on-premises-scim-provisioning.md) with your application and automate provisioning and deprovisioning. If you have legacy applications that don't support SCIM and rely on an [LDAP](./on-premises-ldap-connector-configure.md) user store or a [SQL](./tutorial-ecma-sql-connector.md) database, Azure AD can support these applications as well. 
 
 App provisioning lets you:
 

articles/active-directory/develop/scenario-web-app-call-api-call-api.md

@@ -150,7 +150,7 @@ public async Task<IActionResult> Profile()
 > [!NOTE]
 > You can use the same principle to call any web API.
 >
-> Most Azure web APIs provide an SDK that simplifies calling the API as is the case for Microsoft Graph. See, for instance, [Create a web application that authorizes access to Blob storage with Azure AD](../../storage/common/storage-auth-aad-app.md?tabs=dotnet&toc=%2fazure%2fstorage%2fblobs%2ftoc.json) for an example of a web app using Microsoft.Identity.Web and using the Azure Storage SDK.
+> Most Azure web APIs provide an SDK that simplifies calling the API as is the case for Microsoft Graph.
 
 # [Java](#tab/java)
 

articles/active-directory/hybrid/TOC.yml

@@ -68,11 +68,11 @@
        href: how-to-connect-fed-compatibility.md
    - name: Single sign-on
      items:
-     - name: What is Single Sign-On?
+     - name: What is single sign-on?
        href: how-to-connect-sso.md
-     - name: How Single Sign-On works
+     - name: How single sign-on works
        href: how-to-connect-sso-how-it-works.md
-     - name: Single Sign-On and user privacy
+     - name: Single sign-on and user privacy
        href: how-to-connect-sso-user-privacy.md
    - name: Azure AD Connect Sync
      items:
@@ -105,19 +105,19 @@
     items:
     - name: Installation Roadmap
       href: how-to-connect-install-roadmap.md
-    - name: Installation Prerequisites
+    - name: Installation prerequisites
       href: how-to-connect-install-prerequisites.md
     - name: Choose the installation type
       href: how-to-connect-install-select-installation.md
-    - name: Install Azure AD Connect with Express settings (Password Hash Synch)
+    - name: Install Azure AD Connect with Express settings (password hash sync)
       href:  how-to-connect-install-express.md
-    - name: Install Azure AD Connect Federation or other Custom settings
+    - name: Install Azure AD Connect federation or other Custom settings
       href:  how-to-connect-install-custom.md
     - name: Import and export configuration settings
       href:  how-to-connect-import-export-config.md
-    - name: Install Azure AD Connect with Pass-through Authentication (PTA)
+    - name: Install Azure AD Connect with pass-through authentication
       href:  how-to-connect-pta-quick-start.md 
-    - name: Install Azure AD Connect Health
+    - name: Install Azure AD Connect Health agents
       href:  how-to-connect-health-agent-install.md
     - name: Automatic upgrade
       href: how-to-connect-install-automatic-upgrade.md
@@ -151,7 +151,7 @@
       href: plan-connect-topologies.md
     - name: Factors influencing the performance of Azure AD Connect
       href: plan-connect-performance-factors.md
-    - name: How will users sign-in
+    - name: How will users sign in
       href: plan-connect-user-signin.md
     - name: Azure AD UserPrincipalName population
       href: plan-connect-userprincipalname.md
@@ -259,10 +259,10 @@
   - name: Manage single sign-on 
     items:
 
-    - name: Get started with Single Sign-On
+    - name: Get started with Seamless single sign-on
       href: how-to-connect-sso-quick-start.md
 
-    - name: Single Sign-On FAQ
+    - name: Single sign-on FAQ
       href: how-to-connect-sso-faq.yml
   - name: Manage Azure AD Connect Health
     items: