Merge pull request #241058 from MicrosoftDocs/main

6/09/2023 10AM Publishing

Author: huypub

.openpublishing.redirection.active-directory.json

@@ -12093,6 +12093,12 @@
       "redirect_url": "/azure/active-directory/hybrid/connect/how-to-connect-sync-change-serviceacct-pass",
       "redirect_document_id": false
       },
+
+      {
+        "source_path_from_root": "/articles/active-directory-b2c/azure-ad-external-identities-videos.md",
+        "redirect_url": "/azure/active-directory-b2c/external-identities-videos",
+        "redirect_document_id": true
+      },
 
       {
       "source_path_from_root": "/articles/active-directory/hybrid/how-to-connect-sync-change-the-configuration.md",
@@ -12679,6 +12685,24 @@
         "redirect_document_id": true
       },
 
+      {
+        "source_path_from_root": "/articles/active-directory/standards/azure-ad-pci-dss-guidance.md",
+        "redirect_url": "/azure/active-directory/standards/pci-dss-guidance",
+        "redirect_document_id": true
+      },
+
+      {
+        "source_path_from_root": "/articles/active-directory/standards/azure-ad-pci-dss-mfa.md",
+        "redirect_url": "/azure/active-directory/standards/pci-dss-mfa",
+        "redirect_document_id": true
+      },
+
+      {
+        "source_path_from_root": "/articles/active-directory/standards/hipaa-configure-azure-active-directory-for-compliance.md",
+        "redirect_url": "/azure/active-directory/standards/hipaa-configure-for-compliance",
+        "redirect_document_id": true
+      },
+
       {
         "source_path_from_root": "/articles/active-directory/fundamentals/secure-with-azure-ad-introduction.md",
         "redirect_url": "/azure/active-directory/fundamentals/secure-introduction",
@@ -12774,6 +12798,18 @@
         "redirect_document_id": true
       },
 
+      {
+        "source_path_from_root": "/articles/active-directory-b2c/azure-sentinel.md",
+        "redirect_url": "/azure/active-directory-b2c/configure-security-analytics-sentinel",
+        "redirect_document_id": true
+      },
+
+      {
+        "source_path_from_root": "/articles/active-directory-b2c/partner-azure-web-application-firewall.md",
+        "redirect_url": "/azure/active-directory-b2c/partner-web-application-firewall",
+        "redirect_document_id": true
+      },
+
       {
       "source_path_from_root": "/articles/active-directory/external-identities/customers/microsoft-graph-operations-custom-extensions.md",
       "redirect_url": "/azure/active-directory/external-identities/customers/microsoft-graph-operations",

.openpublishing.redirection.json

@@ -9037,22 +9037,7 @@
             "source_path_from_root": "/articles/container-instances/container-instances-quotas.md",
             "redirect_url": "/azure/container-instances/container-instances-resource-and-quota-limits",
             "redirect_document_id": false
-        },
-        {
-            "source_path_from_root": "/articles/container-instances/container-instances-tutorial-deploy-spot-containers-portal.md",
-            "redirect_url": "/azure/container-instances/container-instances-overview",
-            "redirect_document_id": false
-        },   
-        {
-            "source_path_from_root": "/articles/container-instances/container-instances-tutorial-deploy-spot-containers-cli.md",
-            "redirect_url": "/azure/container-instances/container-instances-overview",
-            "redirect_document_id": false
-        },   
-        {
-            "source_path_from_root": "/articles/container-instances/container-instances-spot-containers-overview.md",
-            "redirect_url": "/azure/container-instances/container-instances-overview",
-            "redirect_document_id": false
-        },       
+        },    
         {
             "source_path_from_root": "/articles/container-registry/container-registry-managed-get-started-azure-cli.md",
             "redirect_url": "/azure/container-registry/container-registry-get-started-azure-cli",

articles/active-directory-b2c/TOC.yml

@@ -555,7 +555,7 @@
         - name: Akamai
           href: partner-akamai.md
         - name: Azure WAF
-          href: partner-azure-web-application-firewall.md
+          href: partner-web-application-firewall.md
         - name: Cloudflare
           href: partner-cloudflare.md
       - name: Fraud protection partners
@@ -640,7 +640,7 @@
       - name: Azure Monitor
         href: azure-monitor.md
       - name: Microsoft Sentinel
-        href: azure-sentinel.md
+        href: configure-security-analytics-sentinel.md
         displayName: log, logs, logging, events, Azure Monitor, Microsoft Sentinel, SIEM, threat hunting, Security, Security Orchestration
     - name: Troubleshooting
       items:

articles/active-directory-b2c/azure-ad-external-identities-videos.md

@@ -58,7 +58,7 @@ The **InputClaims** element contains a list of claims to send to Conditional Acc
 | UserId | Yes | string | The identifier of the user who signs in. |
 | AuthenticationMethodsUsed | Yes |stringCollection | The list of methods the user used to sign in. Possible values: `Password`, and `OneTimePasscode`. |
 | IsFederated | Yes |boolean | Indicates whether or not a user signed in with a federated account. The value must be `false`. |
-| IsMfaRegistered | Yes |boolean | Indicates whether the user already enrolled a phone number for multi-factor authentication. |
+| IsMfaRegistered | Yes |boolean | Indicates whether the user already enrolled a method for multi-factor authentication. If the value is set to `false`, the Conditional Access policy evaluation returns a `block` challenge if action is required. |
 
 The **InputClaimsTransformations** element may contain a collection of **InputClaimsTransformation** elements that are used to modify the input claims or generate new ones before sending them to the Conditional Access service.
 

articles/active-directory-b2c/conditional-access-technical-profile.md

@@ -59,12 +59,12 @@ After you configure your Azure AD B2C instance to send logs to Azure Monitor, en
 2. Select the subscription where the Log Analytics workspace is created.
 3. Search for and select **Microsoft Sentinel**.
 
-   ![Screenshot of Azure Sentinel entered into the search field and the Azure Sentinel option that appears.](./media/azure-sentinel/azure-sentinel-add.png)
+   ![Screenshot of Azure Sentinel entered into the search field and the Azure Sentinel option that appears.](./media/configure-security-analytics-sentinel/sentinel-add.png)
 
 3. Select **Add**.
 4. In the **search workspaces** field, select the new workspace.
 
-   ![Screenshot of the search workspaces field under Choose a workspace to add to Azure Sentinel.](./media/azure-sentinel/create-new-workspace.png)
+   ![Screenshot of the search workspaces field under Choose a workspace to add to Azure Sentinel.](./media/configure-security-analytics-sentinel/create-new-workspace.png)
 
 5. Select **Add Microsoft Sentinel**.
 
@@ -89,7 +89,7 @@ Use the following steps to receive notification about two or more unsuccessful,
 1. In Microsoft Sentinel, from the left menu, select **Analytics**.
 2. On the top bar, select **+ Create** > **Scheduled query rule**. 
 
-   ![Screenshot of the Create option under Analytics.](./media/azure-sentinel/create-scheduled-rule.png)
+   ![Screenshot of the Create option under Analytics.](./media/configure-security-analytics-sentinel/create-scheduled-rule.png)
 
 3. In the Analytics Rule wizard, go to **General**.
 4. For **Name**, enter a name for unsuccessful logins.
@@ -98,12 +98,12 @@ Use the following steps to receive notification about two or more unsuccessful,
 7. For **Severity**, select a severity level.
 8. **Status** is **Enabled** by default. To change a rule, go to the **Active rules** tab.
 
-   ![Screenshot of Create new rule with options and selections.](./media/azure-sentinel/create-new-rule.png)
+   ![Screenshot of Create new rule with options and selections.](./media/configure-security-analytics-sentinel/create-new-rule.png)
 
 9. Select the **Set rule logic** tab.
 10. Enter a query in the **Rule query** field. The query example organizes the sign-ins by `UserPrincipalName`.
 
-    ![Screenshot of query text in the Rule query field under Set rule logic.](./media/azure-sentinel/rule-query.png)
+    ![Screenshot of query text in the Rule query field under Set rule logic.](./media/configure-security-analytics-sentinel/rule-query.png)
 
 11. Go to **Query scheduling**.
 12. For **Run query every**, enter **5** and **Minutes**.
@@ -113,12 +113,12 @@ Use the following steps to receive notification about two or more unsuccessful,
 16. For **Stop running query after alert is generated**, select **Off**.
 17. Select **Next: Incident settings (Preview)**. 
 
-   ![Screenshot of Query scheduling selections and options.](./media/azure-sentinel/query-scheduling.png)
+   ![Screenshot of Query scheduling selections and options.](./media/configure-security-analytics-sentinel/query-scheduling.png)
 
 18. Go to the **Review and create** tab to review rule settings. 
 19. When the **Validation passed** banner appears, select **Create**.
 
-    ![Screenshot of selected settings, the Validation passed banner, and the Create option.](./media/azure-sentinel/review-create.png)
+    ![Screenshot of selected settings, the Validation passed banner, and the Create option.](./media/configure-security-analytics-sentinel/review-create.png)
 
 #### View a rule and related incidents
 
@@ -130,7 +130,7 @@ View the rule and the incidents it generates. Find your newly created custom rul
 
 You can edit, enable, disable, or delete the rule.
 
-   ![Screenshot of active rules with Enable, Disable, Delete, and Edit options.](./media/azure-sentinel/rule-crud.png)
+   ![Screenshot of active rules with Enable, Disable, Delete, and Edit options.](./media/configure-security-analytics-sentinel/rule-crud.png)
 
 #### Triage, investigate, and remediate incidents
 
@@ -142,17 +142,17 @@ Learn more: [Investigate incidents with Microsoft Sentinel](../sentinel/investig
 2. Select an incident. 
 3. On the right, detailed incident information appears, including severity, entities, events, and the incident ID.
 
-    ![Screenshot that shows incident information.](./media/azure-sentinel/select-incident.png)
+    ![Screenshot that shows incident information.](./media/configure-security-analytics-sentinel/select-incident.png)
 
 4. On the **Incidents** pane, elect **View full details**. 
 5. Review tabs that summarize the incident.
 
-    ![Screenshot of a list of incidents.](./media/azure-sentinel/full-details.png)
+    ![Screenshot of a list of incidents.](./media/configure-security-analytics-sentinel/full-details.png)
 
 6. Select **Evidence** > **Events** > **Link to Log Analytics**. 
 7. In the results, see the identity `UserPrincipalName` value attempting sign-in.
 
-    ![Screenshot of incident details.](./media/azure-sentinel/logs.png)
+    ![Screenshot of incident details.](./media/configure-security-analytics-sentinel/logs.png)
 
 ## Automated response
 
@@ -170,7 +170,7 @@ For this task, use a playbook from the Microsoft Sentinel GitHub repository.
 
 Learn more: [Incident-Email-Notification](https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks/Incident-Email-Notification)
 
-   ![Screenshot of automated response options for a rule.](./media/azure-sentinel/automation-tab.png)
+   ![Screenshot of automated response options for a rule.](./media/configure-security-analytics-sentinel/automation-tab.png)
 
 ## Resources
 

…s/active-directory-b2c/azure-sentinel.md …configure-security-analytics-sentinel.mdarticles/active-directory-b2c/azure-sentinel.md renamed to articles/active-directory-b2c/configure-security-analytics-sentinel.md articles/active-directory-b2c/azure-sentinel.md renamed to articles/active-directory-b2c/configure-security-analytics-sentinel.md

@@ -352,7 +352,7 @@ After you add the custom domain and configure your application, users will still
 
 ## (Optional) Azure Front Door advanced configuration
 
-You can use Azure Front Door advanced configuration, such as [Azure Web Application Firewall (WAF)](partner-azure-web-application-firewall.md). Azure WAF provides centralized protection of your web applications from common exploits and vulnerabilities.
+You can use Azure Front Door advanced configuration, such as [Azure Web Application Firewall (WAF)](partner-web-application-firewall.md). Azure WAF provides centralized protection of your web applications from common exploits and vulnerabilities.
 
 When using custom domains, consider the following points: