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

Author: dlepow

.gitignore

@@ -25,4 +25,4 @@ AzureMigration.ps1
 **/.vscode/settings.json
 !/.vscode/settings.json
 
-desktop.ini
+desktop.ini

.openpublishing.redirection.json

@@ -0,0 +1,24 @@
+{
+    "$schema": "https://whatsnewapi.azurewebsites.net/schema",
+    "docSetProductName": "Azure Active Directory application proxy",
+    "rootDirectory": "articles/active-directory/app-proxy/",
+    "docLinkSettings": {
+        "linkFormat": "relative",
+        "relativeLinkPrefix": "/azure/active-directory/app-proxy"
+    },
+    "inclusionCriteria": {
+        "excludePullRequestTitles": true,
+        "minAdditionsToFile" : 2,
+        "maxFilesChanged": 50,
+        "labels": [
+            "label:active-directory/svc",
+            "label:app-proxy/subsvc"
+        ]
+    },
+    "areas": [
+        {
+            "name": ".",
+            "heading": "Azure Active Directory application proxy"
+        }
+    ]
+}

.whatsnew/.application-proxy.json

@@ -7,7 +7,7 @@
         "relativeLinkPrefix": "/azure/active-directory/develop"
     },
     "inclusionCriteria": {
-        "excludePullRequestTitles": true,
+        "omitPullRequestTitles" : true,
         "minAdditionsToFile" : 20,
         "maxFilesChanged": 50,
         "labels": [
@@ -17,7 +17,7 @@
     },
     "areas": [
         {
-            "name": ".",
+            "names": [ "."],
             "heading": "Microsoft identity platform"
         }
     ]

.whatsnew/.microsoft-identity-platform.json

@@ -57,6 +57,10 @@ articles/terraform/ @TomArcherMsft
 articles/virtual-machines/ @cynthn @mimckitt
 articles/virtual-machine-scale-sets/ @ju-shim @mimckitt
 articles/cloud-services/ @mimckitt
+articles/cloud-services-extended-support/ @mimckitt
+articles/service-fabric/ @erikadoyle @mimckitt
+articles/container-instances/ @macolso @mimckitt
+articles/container-registry/ @dlepow @mimckitt
 
 # Requires Internal Review
 articles/best-practices-availability-paired-regions.md @martinekuan @syntaxc4 @snoviking

CODEOWNERS

@@ -88,6 +88,9 @@
       href: user-flow-overview.md
     - name: Custom policy overview
       href: custom-policy-overview.md
+  - name: API Connectors
+    href: api-connectors-overview.md
+    displayName: REST API, web API, API connectors
   - name: User accounts
     href: user-overview.md
   - name: User profile attributes
@@ -171,6 +174,8 @@
       href: identity-provider-azure-ad-multi-tenant.md
     - name: Azure AD B2C
       href: identity-provider-azure-ad-b2c.md
+    - name: eBay
+      href: identity-provider-ebay.md
     - name: Facebook
       href: identity-provider-facebook.md
     - name: Generic OpenId Connect
@@ -277,26 +282,18 @@
       href: conditional-access-user-flow.md
   - name: Configure age gating
     href: age-gating.md
-  - name: API connectors (preview)
+  - name: API connectors
     items:
-    - name: Overview
-      href: api-connectors-overview.md
-    - name: Add an API connector
+    - name: Add an API connector to a sign-up user flow
       href: add-api-connector.md
+      displayName: rest claims validation, validate
+    - name: Add an API connector to a sign-up or sign-in user flow
+      href: custom-policy-rest-api-claims-exchange.md
+      displayName: rest claims exchange
+    - name: Secure an API connector
+      href: secure-rest-api.md
   - name: Custom policy
     items:
-    - name: Add your own business logic
-      items:
-      - name: Integrate REST API
-        href: custom-policy-rest-api-intro.md
-      - name: Validate user input
-        href: custom-policy-rest-api-claims-validation.md
-        displayName: rest claims validation, validate
-      - name: Obtain additional claims
-        href: custom-policy-rest-api-claims-exchange.md
-        displayName: rest claims exchange
-      - name: Secure REST API
-        href: secure-rest-api.md
     - name: Troubleshooting
       items:
       - name: Collect logs using Application Insights
@@ -505,10 +502,12 @@
       href: relyingparty.md
     - name: Claim resolvers
       href: claim-resolver-overview.md
-  - name: Custom policy release notes
+  - name: Release notes
     href: custom-policy-developer-notes.md
   - name: Service limits and restrictions
     href: service-limits.md
+  - name: TLS and cipher suite requirements
+    href: https-cipher-tls-requirements.md
   - name: App registrations
     href: app-registrations-training-guide.md
   - name: Billing model

articles/active-directory-b2c/TOC.yml

@@ -6,7 +6,7 @@ author: msmimart
 manager: celestedg
 
 ms.author: mimart
-ms.date: 03/03/2021
+ms.date: 04/29/2021
 ms.custom: mvc
 ms.topic: how-to
 ms.service: active-directory
@@ -35,6 +35,7 @@ You typically use only one identity provider in your applications, but you have
 * [Azure AD (Single-tenant)](identity-provider-azure-ad-single-tenant.md)
 * [Azure AD (Multi-tenant)](identity-provider-azure-ad-multi-tenant.md)
 * [Azure AD B2C](identity-provider-azure-ad-b2c.md)
+* [eBay](identity-provider-ebay.md)
 * [Facebook](identity-provider-facebook.md)
 * [Generic identity provider](identity-provider-generic-openid-connect.md)
 * [GitHub](identity-provider-github.md)

articles/active-directory-b2c/add-api-connector.md

@@ -9,7 +9,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
-ms.date: 03/22/2021
+ms.date: 05/03/2021
 ms.author: mimart
 ms.subservice: B2C
 zone_pivot_groups: b2c-policy-type
@@ -156,7 +156,7 @@ In Azure Active Directory B2C (Azure AD B2C), you can enable users who are signe
 
 1. Open the policy that you changed. For example, *B2C_1A_profile_edit_password_change*.
 2. For **Application**, select your application that you previously registered. To see the token, the **Reply URL** should show `https://jwt.ms`.
-3. Click **Run now**. Sign in with the account that you previously created. You should now have the opportunity to change the password.
+3. Click **Run now**. In the new tab that opens, remove "&prompt=login" from the URL and refresh the tab. Then sign in with the account you previously created. You will now have the opportunity to change the password.
 
 ## Next steps