Merge pull request #89693 from MicrosoftDocs/master

9/25 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -1715,6 +1715,66 @@
       "redirect_url": "/azure/cosmos-db/manage-with-powershell",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/cosmos-db/scripts/create-cassandra-database-account-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/cassandra/create",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/create-database-account-collections-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/sql/create",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/create-firewall-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/common/ipfirewall",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/create-gremlin-database-account-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/gremlin/create",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/create-mongodb-database-account-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/mongodb/create",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/create-table-database-account-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/table/create",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/ha-failover-policy.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/common/regions",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/scale-collection-throughput-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/sql/throughput",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/scale-multiregion-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/common/regions",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/secure-get-account-key-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/common/keys",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/secure-mongo-connection-string.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/common/keys",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cosmos-db/scripts/secure-generate-key-cli.md",
+      "redirect_url": "/azure/cosmos-db/scripts/cli/common/keys",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/cosmos-db/programming.md",
       "redirect_url": "/azure/cosmos-db/storedprocedures-triggers-udfs",

articles/active-directory-b2c/active-directory-b2c-reference-tenant-type.md

@@ -1,5 +1,5 @@
 ---
-title: Region availability & data residency in Azure Active Directory B2C | Microsoft Docs
+title: Region availability & data residency in Azure Active Directory B2C
 description: A topic on the types of Azure Active Directory B2C tenants.
 services: active-directory-b2c
 author: mmacy
@@ -8,50 +8,59 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 04/10/2017
+ms.date: 09/26/2019
 ms.author: marsma
 ms.subservice: B2C
 ---
 
 # Azure Active Directory B2C: Region availability & data residency
-Region availability and data residency are two very different concepts that apply differently to Azure AD B2C from the rest of Azure. This article will explain the differences between these two concepts and compare how they apply to Azure versus Azure AD B2C.
 
-## Summary
-Azure AD B2C is **generally available worldwide** with the option for **data residency in United States or Europe**.
+Region availability and data residency are two very different concepts that apply differently to Azure AD B2C from the rest of Azure. This article explains the differences between these two concepts, and compares how they apply to Azure versus Azure AD B2C.
 
-## Concepts
-* **Region availability** refers to where a service is available for use.
-* **Data residency** refers to where user data is stored.
+Azure AD B2C is **generally available worldwide** with the option for **data residency** in the **United States, Europe, or Asia Pacific**.
+
+[Region availability](#region-availability) refers to where a service is available for use.
+
+[Data residency](#data-residency) refers to where user data is stored.
 
 ## Region availability
-Azure AD B2C is available worldwide via the Azure public cloud. 
 
-This differs from the model most other Azure services follow which couple availability with data residency. You can see examples of this in both Azure's [Products Available By Region](https://azure.microsoft.com/regions/services/) page and the [Active Directory B2C pricing calculator](https://azure.microsoft.com/pricing/details/active-directory-b2c/).
+Azure AD B2C is available worldwide via the Azure public cloud.
+
+This differs from the model followed by most other Azure services, which typically couple *availability* with *data residency*. You can see examples of this in both Azure's [Products Available By Region](https://azure.microsoft.com/regions/services/) page and the [Active Directory B2C pricing calculator](https://azure.microsoft.com/pricing/details/active-directory-b2c/).
 
 ## Data residency
-Azure AD B2C stores user data in either United States or Europe.
 
-Data residency is determined based on which country/region is selected when [creating an Azure AD B2C tenant](active-directory-b2c-get-started.md).
+Azure AD B2C stores user data in either United States, Europe, or the Asia Pacific region.
+
+Data residency is determined by the country/region you select when you [create an Azure AD B2C tenant](active-directory-b2c-get-started.md):
 
 ![Screenshot of a preview tenant](./media/active-directory-b2c-reference-tenant-type/data-residency-b2c-tenant.png)
 
-Data resides in the United States for the following countries/regions:
+Data resides in the **United States** for the following countries/regions:
 
 > United States, Canada, Costa Rica, Dominican Republic, El Salvador, Guatemala, Mexico, Panama, Puerto Rico and Trinidad & Tobago
 
-Data resides in Europe for the following countries/regions:
+Data resides in **Europe** for the following countries/regions:
 
-> Algeria, Austria, Azerbaijan, Bahrain, Belarus, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Egypt, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Israel, Italy, Jordan, Kazakhstan, Kenya, Kuwait, Lativa, Lebanon, Liechtenstein, Lithuania, Luxembourg, North Macedonia, Malta, Montenegro, Morocco, Netherlands, Nigeria, Norway, Oman, Pakistan, Poland, Portugal, Qatar, Romania, Russia, Saudi Arabia, Serbia, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Tunisia, Turkey, Ukraine, United Arab Emirates and United Kingdom.
+> Algeria, Austria, Azerbaijan, Bahrain, Belarus, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Egypt, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Israel, Italy, Jordan, Kazakhstan, Kenya, Kuwait, Latvia, Lebanon, Liechtenstein, Lithuania, Luxembourg, North Macedonia, Malta, Montenegro, Morocco, Netherlands, Nigeria, Norway, Oman, Pakistan, Poland, Portugal, Qatar, Romania, Russia, Saudi Arabia, Serbia, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Tunisia, Turkey, Ukraine, United Arab Emirates and United Kingdom.
 
-The remaining countries/regions are in the process of being added to the list.  For now, you can still use Azure AD B2C by picking any of the countries/regions above.
+Data resides in **Asia Pacific** for the following countries/regions:
 
-> Afghanistan, Argentina, Australia, Brazil, Chile, Colombia, Ecuador, Hong Kong SAR, India, Indonesia, Iraq, Japan, Korea, Malaysia, New Zealand, Paraguay, Peru, Philippines, Singapore, Sri Lanka, Taiwan, Thailand, Uruguay and Venezuela.
+> Afghanistan, Hong Kong SAR, India, Indonesia, Japan, Korea, Malaysia, Philippines, Singapore, Sri Lanka, Taiwan, and Thailand.
+
+The following countries/regions are in the process of being added to the list. For now, you can still use Azure AD B2C by picking any of the countries/regions above.
+
+> Argentina, Australia, Brazil, Chile, Colombia, Ecuador, Iraq, New Zealand, Paraguay, Peru, Uruguay, and Venezuela.
 
 ## Preview tenant
-If you had created a B2C tenant during Azure AD B2C's preview period, it is likely that your **Tenant type** says **Preview tenant**. If this is the case, you MUST use your tenant only for development and testing purposes, and NOT for production apps.
 
-> [!IMPORTANT]
-> There is no migration path from a preview B2C tenant to a production-scale B2C tenant. Note that there are known issues when you delete a preview B2C tenant and re-create a production-scale B2C tenant with the same domain name. You have to create a production-scale B2C tenant with a different domain name.
+If you had created a B2C tenant during Azure AD B2C's preview period, it's likely that your **Tenant type** says **Preview tenant**.
+
+If this is the case, you must use your tenant ONLY for development and testing purposes. DO NOT use a preview tenant for production applications.
+
+**There is no migration path** from a preview B2C tenant to a production-scale B2C tenant. You must create a new B2C tenant for your production applications.
 
+There are known issues when you delete a preview B2C tenant and create a production-scale B2C tenant with the same domain name. *You must create a production-scale B2C tenant with a different domain name*.
 
-![Screenshot of a preview tenant](./media/active-directory-b2c-reference-tenant-type/preview-b2c-tenant.png)
+![Screenshot of a preview tenant](./media/active-directory-b2c-reference-tenant-type/preview-b2c-tenant.png)

articles/active-directory-b2c/media/active-directory-b2c-reference-tenant-type/data-residency-b2c-tenant.png

@@ -65,7 +65,7 @@ Depending on how your client is built, it can use one (or several) of the authen
 |-----|----------|----------|--------------|---------------|--------------------|
 |[Authorization code flow](v2-oauth2-auth-code-flow.md) | | x | x | x | x|  
 |[Implicit flow](v2-oauth2-implicit-grant-flow.md) | | x        | x    |      |                    |
-|[Hybrid OIDC flow](v2-protocols-oidc.md#get-access-tokens)| | x  | |          |               | x|
+|[Hybrid OIDC flow](v2-protocols-oidc.md#get-access-tokens)| | x  | |          |            x   |
 |[Refresh token redemption](v2-oauth2-auth-code-flow.md#refresh-the-access-token) | refresh token | x | x | x| |
 |[On-behalf-of flow](v2-oauth2-on-behalf-of-flow.md) | access token| x| x| x| |
 |[Device code flow](v2-oauth2-device-code.md) | | x| x| x| |

articles/active-directory/develop/authentication-scenarios.md

@@ -87,7 +87,7 @@ If you need additional permissions or resources supported, which you don’t cur
 New provisioning logs are available to help you monitor and troubleshoot the user and group provisioning deployment. These new log files include information about:
 
 - What groups were successfully created in [ServiceNow](https://docs.microsoft.com/azure/active-directory/saas-apps/servicenow-provisioning-tutorial)
-- What roles were imported from [Amazon Web Services (AWS)](https://docs.microsoft.com/azure/active-directory/saas-apps/amazon-web-service-tutorial#configure-and-test-azure-ad-single-sign-on)
+- What roles were imported from [Amazon Web Services (AWS)](https://docs.microsoft.com/azure/active-directory/saas-apps/amazon-web-service-tutorial#configure-and-test-azure-ad-single-sign-on-for-amazon-web-services-aws)
 - What employees weren't imported from [Workday](https://docs.microsoft.com/azure/active-directory/saas-apps/workday-inbound-tutorial)
 
 For more information, see [Provisioning reports in the Azure Active Directory portal (preview)](https://docs.microsoft.com/azure/active-directory/reports-monitoring/concept-provisioning-logs).

articles/active-directory/fundamentals/whats-new.md

@@ -91,7 +91,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 1. Click **Set additional URLs** and perform the following steps if you wish to configure the application in **SP** initiated mode:
 
     In the **Sign-on URL** text box, type a URL:
-    `https://cas.idc.com/saml-welcome/AzureAppDirectory`
+    `https://www.idc.com/saml-welcome/<SamlWelcomeCode>`
 
     > [!NOTE]
     > These values are not real. Update these values with the actual Identifier and Reply URL. Contact [IDC Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
@@ -140,7 +140,7 @@ To configure single sign-on on **IDC** side, you need to send the downloaded **F
 
 ### Create IDC test user
 
-In this section, you create a user called Britta Simon in IDC. Work with [IDC support team](mailto:[email protected]) to add the users in the IDC platform. Users must be created and activated before you use single sign-on.
+A user does not have to be created in IDC in advance. The user will created automatically once he uses single sign-on for the first time.
 
 ## Test SSO 
 

articles/active-directory/saas-apps/idc-tutorial.md

@@ -118,7 +118,7 @@ The `rate-limit` policy prevents API usage spikes on a per subscription basis by
 
 | Name      | Description                                                                                                                                                                                                                                                                                              | Required |
 | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
-| set-limit | Root element.                                                                                                                                                                                                                                                                                            | Yes      |
+| rate-limit | Root element.                                                                                                                                                                                                                                                                                            | Yes      |
 | api       | Add one or more of these elements to impose a call rate limit on APIs within the product. Product and API call rate limits are applied independently. API can be referenced either via `name` or `id`. If both attributes are provided, `id` will be used and `name` will be ignored.                    | No       |
 | operation | Add one or more of these elements to impose a call rate limit on operations within an API. Product, API, and operation call rate limits are applied independently. Operation can be referenced either via `name` or `id`. If both attributes are provided, `id` will be used and `name` will be ignored. | No       |
 
@@ -181,9 +181,9 @@ In the following example, the rate limit is keyed by the caller IP address.
 
 ### Elements
 
-| Name      | Description   | Required |
-| --------- | ------------- | -------- |
-| set-limit | Root element. | Yes      |
+| Name              | Description   | Required |
+| ----------------- | ------------- | -------- |
+| rate-limit-by-key | Root element. | Yes      |
 
 ### Attributes
 

articles/api-management/api-management-access-restriction-policies.md

@@ -15,7 +15,7 @@ ms.tgt_pltfrm: cache
 ms.workload: tbd
 ms.date: 05/23/2018
 ms.author: yegu
-ms.custom: mvc, seo-java-august2019
+ms.custom: mvc, seo-java-august2019, seo-java-september2019
 #Customer intent: As a Java developer, new to Azure Cache for Redis, I want to create a new Java app that uses Azure Cache for Redis.
 ---
 
@@ -132,7 +132,7 @@ mvn exec:java -D exec.mainClass=example.demo.App
 
 In the example below, you can see the `Message` key previously had a cached value, which was set using the Redis Console in the Azure portal. The app updated that cached value. The app also executed the `PING` and `CLIENT LIST` commands.
 
-![Cache app completed](./media/cache-java-get-started/cache-app-complete.png)
+![Azure Cache for Redis app completed](./media/cache-java-get-started/azure-cache-redis-complete.png)
 
 ## Clean up resources
 
@@ -148,7 +148,7 @@ Otherwise, if you are finished with the quickstart sample application, you can d
 
 1. In the **Filter by name** textbox, type the name of your resource group. The instructions for this article used a resource group named *TestResources*. On your resource group in the result list, select **...** then **Delete resource group**.
 
-   ![Delete](./media/cache-java-get-started/cache-delete-resource-group.png)
+   ![Azure resource group deleted](./media/cache-java-get-started/azure-cache-redis-delete-resource-group.png)
 
 1. You will be asked to confirm the deletion of the resource group. Type the name of your resource group to confirm, and select **Delete**.