Merge pull request #301 from MicrosoftDocs/master

rmerge

Author: MatchaMatch

.github/workflows/stale.yml

@@ -2,7 +2,7 @@ name: Mark stale pull requests
 
 on:
   schedule:
-  - cron: "0 */6 * * *"
+  - cron: "0 */4 * * *"
 
 jobs:
   stale:
@@ -18,9 +18,8 @@ jobs:
         stale-pr-label: inactive
         close-pr-label: auto-close
         exempt-pr-labels: keep-open
-        operations-per-run: 800
-        ascending: true
-        start-date: '2021-07-13'
+        operations-per-run: 1200
+        ascending: false
         stale-pr-message: >
           This pull request has been inactive for at least 14 days.
           If you are finished with your changes, don't forget to sign off. See the [contributor guide](https://review.docs.microsoft.com/help/contribute/contribute-how-to-write-pull-request-automation) for instructions.

.openpublishing.publish.config.json

@@ -357,6 +357,12 @@
       "branch": "main",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "media-services-v3-dotnet-core-functions-integration",
+      "url": "https://github.com/Azure-Samples/media-services-v3-dotnet-core-functions-integration",
+      "branch": "main",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "samples-javascript",
       "url": "https://github.com/Microsoft/tsiclient",
@@ -816,6 +822,7 @@
     ".openpublishing.redirection.healthcare-apis.json",
     ".openpublishing.redirection.media-services.json",
     ".openpublishing.redirection.security-benchmark.json",
+    ".openpublishing.redirection.synapse-analytics.json",
     ".openpublishing.redirection.key-vault.json",
     ".openpublishing.redirection.iot-hub.json",
     "articles/azure-relay/.openpublishing.redirection.relay.json",
@@ -831,6 +838,7 @@
     "articles/iot-develop/.openpublishing.redirection.iot-develop.json",
     "articles/iot-edge/.openpublishing.redirection.iot-edge.json",
     "articles/marketplace/.openpublishing.redirection.marketplace.json",
+    "articles/object-anchors/.openpublishing.redirection.object-anchors.json",
     "articles/purview/.openpublishing.redirection.purview.json",
     "articles/virtual-machines/.openpublishing.redirection.virtual-machines.json",
     "articles/service-bus-messaging/.openpublishing.redirection.service-bus-messaging.json",

.openpublishing.redirection.healthcare-apis.json

@@ -454,7 +454,7 @@
     },
     {
         "source_path_from_root": "/articles/healthcare-apis/azure-api-for-fhir/access-fhir-postman-tutorial.md",
-        "redirect_url": "/azure/healthcare-apis/fhir/using-postman",
+        "redirect_url": "/azure/healthcare-apis/use-postman",
         "redirect_document_id": true
     }
   ]

.openpublishing.redirection.json

@@ -489,6 +489,22 @@
       "source_path_from_root": "/articles/key-vault/general/key-vault-integrate-kubernetes.md",
       "redirect_url": "/azure/aks/csi-secrets-store-driver",
       "redirect_document_id": false
+    },
+
+    {
+      "source_path_from_root": "/articles/key-vault/general/assign-access-policy-portal.md",
+      "redirect_url": "/azure/key-vault/general/assign-access-policy",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/key-vault/general/assign-access-policy-cli.md",
+      "redirect_url": "/azure/key-vault/general/assign-access-policy",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/key-vault/general/assign-access-policy-powershell.md",
+      "redirect_url": "/azure/key-vault/general/assign-access-policy",
+      "redirect_document_id": false
     }
 
   ]

.openpublishing.redirection.key-vault.json

@@ -0,0 +1,44 @@
+{
+    "redirections": [
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-partner-browse-partners.md",
+            "redirect_url": "/azure/synapse-analytics/partner/browse-partners",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-partner-business-intelligence.md",
+            "redirect_url": "/azure/synapse-analytics/partner/business-intelligence",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-partner-compatibility-issues.md",
+            "redirect_url": "/azure/synapse-analytics/partner/compatibility-issues",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-partner-data-integration.md",
+            "redirect_url": "/azure/synapse-analytics/partner/data-integration",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-partner-data-management.md",
+            "redirect_url": "/azure/synapse-analytics/partner/data-management",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-partner-machine-learning-ai.md",
+            "redirect_url": "/azure/synapse-analytics/partner/machine-learning-ai",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-partner-system-integration.md",
+            "redirect_url": "/azure/synapse-analytics/partner/system-integration",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/guidance-for-loading-data.md",
+            "redirect_url": "/azure/synapse-analytics/sql/data-loading-best-practices",
+            "redirect_document_id": false
+        }
+    ]
+}

.openpublishing.redirection.synapse-analytics.json

@@ -332,15 +332,23 @@
       href: configure-tokens.md
   - name: Define custom attributes
     href: user-flow-custom-attributes.md
-  - name: Security and threat management
+  - name: Security
     items:
-    - name: Investigate risk with Identity Protection
-      href: identity-protection-investigate-risk.md
-    - name: Configure Conditional Access
-      href: conditional-access-user-flow.md
-    - name: Mitigate credential attacks
-      displayName: smart lockout, account lockout, password attack
-      href: threat-management.md
+    - name: Monitoring and threat management
+      items:
+      - name: Azure Monitor
+        href: azure-monitor.md
+      - name: Azure Sentinel
+        href: azure-sentinel.md
+        displayName: log, logs, logging, events, Azure Monitor, Azure Sentinel, SIEM, threat hunting, Security, Security Orchestration
+    - name: Web Application Firewall partners
+      items:
+      - name: Akamai
+        href: partner-akamai.md
+      - name: Azure WAF
+        href: partner-azure-web-application-firewall.md
+      - name: Cloudflare
+        href: partner-cloudflare.md
     - name: Fraud protection partners
       items: 
       - name: Arkose Labs
@@ -352,6 +360,28 @@
       - name: Microsoft Dynamics 365 Fraud Protection
         href: partner-dynamics-365-fraud-protection.md
         displayName: m365 dynamics, dynamics fraud protection, fraud, 365 protection
+    - name: Investigate risk with Identity Protection
+      href: identity-protection-investigate-risk.md
+    - name: Configure Conditional Access
+      href: conditional-access-user-flow.md
+    - name: Mitigate credential attacks
+      displayName: smart lockout, account lockout, password attack
+      href: threat-management.md
+    - name: Secure phone-based MFA
+      href: phone-based-mfa.md
+      displayName: multi-factor authentication, Azure Monitor, Log Analytics, reports, reporting, dashboard
+    - name: Secure access to legacy and on-premises apps
+      items:
+      - name: Datawiza
+        href: partner-datawiza.md
+      - name: Ping Identity
+        href: partner-ping-identity.md
+      - name: Strata
+        href: partner-strata.md
+        displayName: AAD b2c access, legacy app, onpremises apps
+      - name: Zscaler
+        href: partner-zscaler.md
+        displayName: zscaler b2c, vpn, sdp b2c
   - name: Configure age gating
     href: age-gating.md
   - name: API connectors
@@ -394,32 +424,12 @@
       href: partner-lexisnexis.md
     - name: Onfido
       href: partner-onfido.md
-  - name: Secure access to legacy and on-premises apps
-    items:
-    - name: Datawiza
-      href: partner-datawiza.md
-    - name: Ping Identity
-      href: partner-ping-identity.md
-    - name: Strata
-      href: partner-strata.md
-      displayName: AAD b2c access, legacy app, onpremises apps
-    - name: Zscaler
-      href: partner-zscaler.md
-      displayName: zscaler b2c, vpn, sdp b2c
   - name: Domain name
     items:
     - name: b2clogin.com overview
       href: b2clogin.md
     - name: Configure a custom domain
       href: custom-domain.md
-    - name: Web Application Firewall partners
-      items:
-      - name: Akamai
-        href: partner-akamai.md
-      - name: Azure WAF
-        href: partner-azure-web-application-firewall.md
-      - name: Cloudflare
-        href: partner-cloudflare.md
     - name: Configure web API domains 
       href: multiple-token-endpoints.md
       displayName: migrate, b2clogin, owin
@@ -450,23 +460,14 @@
         href: partner-n8identity.md
       - name: Saviynt 
         href: partner-saviynt.md
-  - name: Logs and monitoring
+  - name: Logs 
     items:
     - name: Audit logs
       href: view-audit-logs.md
-      displayName: log, logs, logging, usage, events, reports, reporting
-    - name: Azure Monitor
-      href: azure-monitor.md
       displayName: log, logs, logging, usage, events, reports, reporting, dashboard
-    - name: Azure Sentinel
-      href: azure-sentinel.md
-      displayName: log, logs, logging, events, Azure Monitor, Azure Sentinel, SIEM, threat hunting, Security, Security Orchestration
     - name: Usage analytics
       href: analytics-with-application-insights.md
       displayName: application insights, app insights, reports, reporting
-    - name: Secure phone-based MFA
-      href: phone-based-mfa.md
-      displayName: multi-factor authentication, Azure Monitor, Log Analytics, reports, reporting, dashboard
   - name: Compliance
     items:
     - name: User access

articles/active-directory-b2c/TOC.yml

@@ -5,7 +5,7 @@ services: active-directory-b2c
 ms.service: active-directory
 ms.subservice: B2C
 ms.topic: how-to
-ms.date: 05/03/2021
+ms.date: 08/24/2021
 
 ms.author: mimart
 author: msmimart
@@ -41,18 +41,18 @@ You can also design the interaction as an orchestration step. This is suitable w
 To use an [API connector](api-connectors-overview.md), you first create the API connector and then enable it in a user flow.
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
-2. Under **Azure services**, select **Azure AD B2C**.
-4. Select **API connectors**, and then select **New API connector**.
+1. Under **Azure services**, select **Azure AD B2C**.
+1. Select **API connectors**, and then select **New API connector**.
 
    ![Screenshot of basic configuration for an API connector](media/add-api-connector/api-connector-new.png)
 
-5. Provide a display name for the call. For example, **Validate user information**.
-6. Provide the **Endpoint URL** for the API call.
-7. Choose the **Authentication type** and configure the authentication information for calling your API. Learn how to [Secure your API Connector](secure-rest-api.md).
+1. Provide a display name for the call. For example, **Validate user information**.
+1. Provide the **Endpoint URL** for the API call.
+1. Choose the **Authentication type** and configure the authentication information for calling your API. Learn how to [Secure your API Connector](secure-rest-api.md).
 
    ![Screenshot of authentication configuration for an API connector](media/add-api-connector/api-connector-config.png)
 
-8. Select **Save**.
+1. Select **Save**.
 
 ## The request sent to your API
 An API connector materializes as an **HTTP POST** request, sending user attributes ('claims') as key-value pairs in a JSON body. Attributes are serialized similarly to [Microsoft Graph](/graph/api/resources/user#properties) user properties. 
@@ -109,17 +109,17 @@ Additionally, these claims are typically sent in all requests:
 Follow these steps to add an API connector to a sign-up user flow.
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
-2. Under **Azure services**, select **Azure AD B2C**.
-4. Select **User flows**, and then select the user flow you want to add the API connector to.
-5. Select **API connectors**, and then select the API endpoints you want to invoke at the following steps in the user flow:
+1. Under **Azure services**, select **Azure AD B2C**.
+1. Select **User flows**, and then select the user flow you want to add the API connector to.
+1. Select **API connectors**, and then select the API endpoints you want to invoke at the following steps in the user flow:
 
    - **After federating with an identity provider during sign-up**
    - **Before creating the user**
    - **Before sending the token (preview)**
 
    ![Selecting an API connector for a step in the user flow](media/add-api-connector/api-connectors-user-flow-select.png)
 
-6. Select **Save**.
+1. Select **Save**.
 
 These steps only exist for **Sign up and sign in (Recommended)** and **Sign up (Recommended)** but only apply to the sign-up part of the experience.