Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

.openpublishing.redirection.active-directory.json

@@ -11221,6 +11221,11 @@
       "redirect_url": "/azure/active-directory/privileged-identity-management/pim-create-azure-ad-roles-and-resource-roles-review",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/active-directory-b2c/user-manage-inactive.md",
+      "redirect_url": "/azure/active-directory-b2c/manage-users-portal",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/active-directory-b2c/troubleshoot-custom-policies.md",
       "redirect_url": "/azure/active-directory-b2c/troubleshoot",
@@ -12892,7 +12897,94 @@
         "source_path_from_root": "/articles/active-directory/authentication/active-directory-certificate-based-authentication-get-started.md",
         "redirect_url": "/azure/active-directory/authentication/certificate-based-authentication-federation-get-started",
         "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-access-create-new-tenant.md",
+        "redirect_url": "/azure/active-directory/fundamentals/create-new-tenant",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-architecture.md",
+        "redirect_url": "/azure/active-directory/fundamentals/architecture",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-data-storage-australia.md",
+        "redirect_url": "/azure/active-directory/fundamentals/data-storage-australia",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-data-storage-australia-newzealand.md",
+        "redirect_url": "/azure/active-directory/fundamentals/data-storage-australia-newzealand",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-data-storage-eu.md",
+        "redirect_url": "/azure/active-directory/fundamentals/data-storage-eu",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-faq.yml",
+        "redirect_url": "/azure/active-directory/fundamentals/faq",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-data-storage-japan.md",
+        "redirect_url": "/azure/active-directory/fundamentals/data-storage-japan",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-get-started-premium.md",
+        "redirect_url": "/azure/active-directory/fundamentals/get-started-premium",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-groups-view-azure-portal.md",
+        "redirect_url": "/azure/active-directory/fundamentals/groups-view-azure-portal",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md",
+        "redirect_url": "/azure/active-directory/fundamentals/how-subscriptions-associated-directory",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-how-to-find-tenant.md",
+        "redirect_url": "/azure/active-directory/fundamentals/how-to-find-tenant.md",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-users-assign-role-azure-portal.md",
+        "redirect_url": "/azure/active-directory/fundamentals/how-subscriptions-associated-directory",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-properties-area.md",
+        "redirect_url": "/azure/active-directory/fundamentals/properties-area",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-licensing-whatis-azure-portal.md",
+        "redirect_url": "/azure/active-directory/fundamentals/licensing-whatis-azure-portal",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-users-reset-password-azure-portal.md",
+        "redirect_url": "/azure/active-directory/fundamentals/users-reset-password-azure-portal",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/active-directory/fundamentals/active-directory-users-restore.md",
+        "redirect_url": "/azure/active-directory/fundamentals/users-restore",
+        "redirect_document_id": false
       }
 
+      
+      
+      
+      
+      
+      
+      
       ]
 } 

.openpublishing.redirection.defender-for-cloud.json

@@ -480,6 +480,11 @@
             "redirect_url": "/azure/defender-for-cloud/enable-enhanced-security",
             "redirect_document_id": true
         },
+        {
+            "source_path_from_root": "/articles/defender-for-cloud/enable-enhanced-security.md",
+            "redirect_url": "/azure/defender-for-cloud/enable-all-plans",
+            "redirect_document_id": true
+        },
         {
             "source_path_from_root": "/articles/security-center/enhanced-security-features-overview.md",
             "redirect_url": "/azure/defender-for-cloud/enhanced-security-features-overview",
@@ -815,6 +820,11 @@
             "redirect_url": "/azure/defender-for-cloud/faq-data-collection-agents",
             "redirect_document_id": true
         },
+        {
+            "source_path_from_root": "/articles/defender-for-cloud/quickstart-enable-database-protections.md",
+            "redirect_url": "/azure/defender-for-cloud/tutorial-enable-databases-plan",
+            "redirect_document_id": true
+        },
         {
             "source_path_from_root": "/articles/defender-for-cloud/defender-for-storage-exclude.md",
             "redirect_url": "/azure/defender-for-cloud/defender-for-storage-classic-enable#exclude-a-storage-account-from-a-protected-subscription-in-the-per-transaction-plan",

articles/active-directory-b2c/TOC.yml

@@ -403,10 +403,7 @@
       displayName: create users, add users, delete users, revoke sessions
     - name: Migrate users
       href: user-migration.md
-      displayName: bulk import
-    - name: Manage inactive users   
-      href: user-manage-inactive.md
-      displayName: Manage and delete inactive users          
+      displayName: bulk import        
     - name: Partner integration
       items:
       - name: N8identity

articles/active-directory-b2c/enable-authentication-web-application-options.md

@@ -303,7 +303,7 @@ To support a secured logout redirect in your application, first follow the steps
 1. In the **Startup.cs** class, parse the `id_token_hint` value and append the value to the authentication request. The following code snippet demonstrates how to pass the `id_token_hint` value to the authentication request:
 
     ```csharp
-    private async Task OnRedirectToIdentityProviderFunc(RedirectContext context)
+    private async Task OnRedirectToIdentityProviderForSignOutFunc(RedirectContext context)
     {
         var id_token_hint = context.Properties.Items.FirstOrDefault(x => x.Key == "id_token_hint").Value;
         if (id_token_hint != null)
@@ -324,7 +324,7 @@ To support a secured logout redirect in your application, first follow the steps
         {
             Configuration.Bind("AzureAdB2C", options);
             options.Events ??= new OpenIdConnectEvents();        
-            options.Events.OnRedirectToIdentityProvider += OnRedirectToIdentityProviderFunc;
+            options.Events.OnRedirectToIdentityProviderForSignOut += OnRedirectToIdentityProviderForSignOutFunc;
             options.SaveTokens = true;
         });
     ```

articles/active-directory-b2c/tenant-management-directory-quota.md

@@ -81,8 +81,4 @@ If your tenant usage is higher that 80%, you can remove inactive users or reques
 
 ## Request increase directory quota size
 
-You can request to increase the quota size by [contacting support](find-help-open-support-ticket.md) 
-
-## Next steps
-
-- Learn [how to manage inactive user accounts](user-manage-inactive.md).
+You can request to increase the quota size by [contacting support](find-help-open-support-ticket.md) 

articles/active-directory-b2c/user-manage-inactive.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.subservice: app-provisioning
 ms.workload: identity
 ms.topic: how-to
-ms.date: 05/04/2023
+ms.date: 06/29/2023
 ms.author: kenwith
 ms.reviewer: arvinh
 ---
@@ -61,16 +61,16 @@ The time it takes for a given user to be provisioned depends mainly on whether y
 The following table summarizes synchronization times for common provisioning scenarios. In these scenarios, the source system is Azure AD and the target system is a SaaS application. The sync times are derived from a statistical analysis of sync jobs for the SaaS applications ServiceNow, Workplace, Salesforce, and G Suite.
 
 
-| Scope configuration | Users, groups, and members in scope | Initial cycle time | Incremental cycle time |
-| -------- | -------- | -------- | -------- |
-| Sync assigned users and groups only |  < 1,000 |  < 30 minutes | < 30 minutes |
-| Sync assigned users and groups only |  1,000 - 10,000 | 142 - 708 minutes | < 30 minutes |
-| Sync assigned users and groups only |   10,000 - 100,000 | 1,170 - 2,340 minutes | < 30 minutes |
-| Sync all users and groups in Azure AD |  < 1,000 | < 30 minutes  | < 30 minutes |
-| Sync all users and groups in Azure AD |  1,000 - 10,000 | < 30 - 120 minutes | < 30 minutes |
-| Sync all users and groups in Azure AD |  10,000 - 100,000  | 713 - 1,425 minutes | < 30 minutes |
-| Sync all users in Azure AD|  < 1,000  | < 30 minutes | < 30 minutes |
-| Sync all users in Azure AD | 1,000 - 10,000  | 43 - 86 minutes | < 30 minutes |
+| Scope configuration | Users, groups, and members in scope | Initial cycle time |
+| -------- | -------- | -------- | 
+| Sync assigned users and groups only |  < 1,000 |  < 30 minutes |
+| Sync assigned users and groups only |  1,000 - 10,000 | 142 - 708 minutes | 
+| Sync assigned users and groups only |   10,000 - 100,000 | 1,170 - 2,340 minutes |
+| Sync all users and groups in Azure AD |  < 1,000 | < 30 minutes  | 
+| Sync all users and groups in Azure AD |  1,000 - 10,000 | < 30 - 120 minutes | 
+| Sync all users and groups in Azure AD |  10,000 - 100,000  | 713 - 1,425 minutes |
+| Sync all users in Azure AD|  < 1,000  | < 30 minutes |
+| Sync all users in Azure AD | 1,000 - 10,000  | 43 - 86 minutes |
 
 For the configuration **Sync assigned user and groups only**, you can use the following formulas to determine the approximate minimum and maximum expected **initial cycle** times:
 
@@ -93,12 +93,7 @@ Summary of factors that influence the time it takes to complete an **initial cyc
 
 - If performance becomes an issue, and you're attempting to provision most users and groups in your tenant, then use scoping filters. Scoping filters allow you to fine tune the data that the provisioning service extracts from Azure AD by filtering out users based on specific attribute values. For more information on scoping filters, see [Attribute-based application provisioning with scoping filters](define-conditional-rules-for-provisioning-user-accounts.md).
 
-The **incremental cycle** may also take longer than the duration we have documented above. Some of the factors that influence this duration are:
-
-- The  number of changes on the individual objects properties.
-- The number of changes on the groups memberships.
-- The scope of assignment configured for the app. Configuration of **sync assigned users and groups only** is recommended where possible.
-
+In most cases, the **incremental cycle** completes in 30 minutes. However, when there are hundreds or thousands of user changes or group membership changes, the incremental cycle time will increase proportionally with the number of changes to process and can take several hours. Using **sync assigned users and groups** and minimizing the number of users / groups in scope for provisioning will help to reduce the sync time.
 
 ## Next steps
 [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](user-provisioning.md)

articles/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md

@@ -0,0 +1,25 @@
+---
+title: Azure AD Provisioning to SAP ERP Central Component (SAP ECC) 7.0
+description: This document describes how to configure Azure AD to provision users into SAP ECC 7.
+services: active-directory
+author: billmath
+manager: amycolannino
+ms.service: active-directory
+ms.subservice: app-provisioning
+ms.topic: how-to
+ms.workload: identity
+ms.date: 06/30/2023
+ms.author: billmath
+ms.reviewer: arvinh
+---
+
+# Configuring Azure AD to provision users into SAP ECC 7.0
+The following documentation provides configuration and tutorial information demonstrating how to provision users from Azure AD into SAP ERP Central Component (SAP ECC) 7.0.  
+
+
+[!INCLUDE [active-directory-app-provisioning-sap.md](../../../includes/active-directory-app-provisioning-sap.md)]
+
+## Next steps
+
+- [App provisioning](user-provisioning.md)
+- [Tutorial: ECMA Connector Host generic SQL connector](tutorial-ecma-sql-connector.md)