Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-role-definitions

Author: rolyon

articles/active-directory-domain-services/network-considerations.md

@@ -105,11 +105,12 @@ The following network security group rules are required for Azure AD DS to provi
 | 443         | TCP      | AzureActiveDirectoryDomainServices | Any         | Allow  | Yes      | Synchronization with your Azure AD tenant. |
 | 3389        | TCP      | CorpNetSaw                         | Any         | Allow  | Yes      | Management of your domain. |
 | 5986        | TCP      | AzureActiveDirectoryDomainServices | Any         | Allow  | Yes      | Management of your domain. |
-| 636         | TCP      | Any                                | Any         | Allow  | No       | Only enabled when you configure secure LDAP (LDAPS). |
 
 > [!WARNING]
 > Don't manually edit these network resources and configurations. When you associate a misconfigured network security group or a user defined route table with the subnet in which Azure AD DS is deployed, you may disrupt Microsoft's ability to service and manage the domain. Synchronization between your Azure AD tenant and your Azure AD DS managed domain is also disrupted.
 >
+> If you use secure LDAP, you can add the required TCP port 636 rule to allow external traffic if needed. Adding this rule doesn't place your network security group rules in an unsupported state. For more information, see [Lock down secure LDAP access over the internet](tutorial-configure-ldaps.md#lock-down-secure-ldap-access-over-the-internet)
+>
 > Default rules for *AllowVnetInBound*, *AllowAzureLoadBalancerInBound*, *DenyAllInBound*, *AllowVnetOutBound*, *AllowInternetOutBound*, and *DenyAllOutBound* also exist for the network security group. Don't edit or delete these default rules.
 >
 > The Azure SLA doesn't apply to deployments where an improperly configured network security group and/or user defined route tables have been applied that blocks Azure AD DS from updating and managing your domain.

articles/aks/api-server-authorized-ip-ranges.md

@@ -37,7 +37,7 @@ For more information about the API server and other cluster components, see [Kub
 API server authorized IP ranges only work for new AKS clusters. Create a cluster using the [az aks create][az-aks-create] and specify the *--api-server-authorized-ip-ranges* parameter to provide a list of authorized IP address ranges. These IP address ranges are usually address ranges used by your on-premises networks or public IPs. When you specify a CIDR range, start with the first IP address in the range. For example, *137.117.106.90/29* is a valid range, but make sure you specify the first IP address in the range, such as *137.117.106.88/29*.
 
 > [!IMPORTANT]
-> By default, your cluster uses the [Standard SKU load balancer][standard-sku-lb] which you can use to configure the outbound gateway. When you enable API server authorized IP ranges during cluster creation, the public IP for your cluster is also allowed by default in addition to the ranges you specify. If you specify *""* or no value for *--api-server-authorized-ip-ranges*, API server authorized IP ranges will be disabled.
+> By default, your cluster uses the [Standard SKU load balancer][standard-sku-lb] which you can use to configure the outbound gateway. When you enable API server authorized IP ranges during cluster creation, the public IP for your cluster is also allowed by default in addition to the ranges you specify. If you specify *""* or no value for *--api-server-authorized-ip-ranges*, API server authorized IP ranges will be disabled. Note that if you're using PowerShell, use *--api-server-authorized-ip-ranges=""* (with equals sign) to avoid any parsing issues.
 
 The following example creates a single-node cluster named *myAKSCluster* in the resource group named *myResourceGroup* with API server authorized IP ranges enabled. The IP address ranges allowed are *73.140.245.0/24*:
 

articles/cosmos-db/managed-identity-based-authentication.md

@@ -61,7 +61,7 @@ In this scenario, the function app will read the temperature of the aquarium, th
 
    * **Role**: Select **DocumentDB Account Contributor**
    * **Assign access to**: Under the **Select system-assigned managed identity** subsection, select **Function App**.
-   * **Select**: The pane will be populated with all the function apps in your subscription that have a **Managed System Identity**. In this case, select the **SummaryService** function app: 
+   * **Select**: The pane will be populated with all the function apps in your subscription that have a **Managed System Identity**. In this case, select the **FishTankTemperatureService** function app: 
 
       ![Screenshot showing the Add role assignment pane populated with examples.](./media/managed-identity-based-authentication/cosmos-db-iam-tab-add-role-pane-filled.png)
 
@@ -79,7 +79,7 @@ This sample uses the [List Keys API](https://docs.microsoft.com/rest/api/cosmos-
 The List Keys API returns the `DatabaseAccountListKeysResult` object. This type isn't defined in the C# libraries. The following code shows the implementation of this class:  
 
 ```csharp 
-namespace SummarizationService 
+namespace Monitor 
 {
   public class DatabaseAccountListKeysResult
   {
@@ -123,7 +123,7 @@ using Microsoft.Extensions.Logging;
 
 namespace Monitor
 {
-    public static class TemperatureMonitor
+    public static class FishTankTemperatureService
     {
         private static string subscriptionId =
         "<azure subscription id>";
@@ -138,7 +138,7 @@ namespace Monitor
         private static string containerName =
         "<container to store the temperature in>";
 
-        [FunctionName("TemperatureMonitor")]
+        [FunctionName("FishTankTemperatureService")]
         public static async Task Run([TimerTrigger("0 * * * * *")]TimerInfo myTimer, ILogger log)
         {
             log.LogInformation($"Starting temperature monitoring: {DateTime.Now}");

articles/cosmos-db/media/managed-identity-based-authentication/cosmos-db-iam-tab-add-role-pane-filled.png

@@ -107,7 +107,7 @@
     href: billing-troubleshoot-azure-payment-issues.md
   - name: Declined card
     href: troubleshoot-declined-card.md
-  - name: Sign up issues
+  - name: Issues in signing up a new account
     href: troubleshoot-azure-sign-up.md
   - name: Subscription sign-in issues
     href: troubleshoot-sign-in-issue.md

articles/cosmos-db/media/managed-identity-based-authentication/cosmos-db-iam-tab.png

@@ -1,26 +1,27 @@
 ---
-title: Troubleshoot Azure sign-up
-description: Resolving an issue when trying to sign-up for a new account in the Microsoft Azure portal account center.
+title: Unable to sign up a new Azure account
+description: Resolving an issue when trying to sign up for a new account in the Microsoft Azure portal account center.
+services: cost-management-billing
 author: v-miegge
-ms.reviewer: dcscontentpm
+manager: dcscontentpm
 tags: billing
 ms.service: cost-management-billing
 ms.topic: conceptual
 ms.date: 02/12/2020
 ms.author: v-miegge
 ---
 
-# Troubleshoot Azure sign-up
+# Troubleshoot issues when you sign up a new account in Azure portal or Azure account center
 
-You may experience an issue when you try to sign-up for a new account in the Microsoft Azure portal or Azure account center. Before you troubleshoot the issue, first verify the following:
+You may experience an issue when you try to sign up for a new account in the Microsoft Azure portal or Azure account center. Before you troubleshoot the issue, first verify the following:
 
 - The information that you provided for your Azure account profile (including contact email address, street address, and telephone number) is correct.
 - The credit card information is correct.
-- You don’t already have a Microsoft account that has the same information.
+- You don't already have a Microsoft account that has the same information.
 
 ## Resolutions
 
-To resolve any errors, select the issue that you experience when you try to sign-up for Azure.
+To resolve any errors, select the issue that you experience when you try to sign up for Azure.
 
 ### Error: *We cannot proceed with sign-up due to an issue with your account. Please contact billing support.*
 
@@ -32,9 +33,9 @@ To resolve the issue, follow these steps:
 
 3. Make sure that all address fields are completed and valid.
 
-4. When you sign-up for the Azure subscription, make sure that the billing address for the credit card registration matches your bank records.
+4. When you sign up for the Azure subscription, make sure that the billing address for the credit card registration matches your bank records.
 
-If you continue to receive the error message, try to sign-up by using a different browser.
+If you continue to receive the error message, try to sign up by using a different browser.
 
 ### Progress bar hangs in *Identity verification by card* section.
 
@@ -79,7 +80,7 @@ Have you used an Azure subscription in the past? The Azure Terms of Use agreemen
 
 ### I saw a charge on my Free Trial account
 
-You may see a small verification hold on your credit card account after you sign-up. This is removed within three to five days. If you are worried about managing costs, read more about [preventing unexpected costs](getting-started.md).
+You may see a small verification hold on your credit card account after you sign up. This is removed within three to five days. If you are worried about managing costs, read more about [preventing unexpected costs](getting-started.md).
 
 ### Can't activate Azure benefit plan like MSDN, BizSpark, BizSparkPlus, or MPN
 
@@ -105,13 +106,13 @@ To resolve this issue, double-check whether the following items are true:
 
 - The information that you provided for your Azure account profile (including contact email address, street address, and telephone number) is correct.
 - The credit card information is correct.
-- You don’t already have a Microsoft account that uses the same information.
+- You don't already have a Microsoft account that uses the same information.
 
 ### Error: *Your current account type is not supported*
 
-This issue can occur if the account is registered in an [unmanaged Azure AD directory](../../active-directory/users-groups-roles/directory-self-service-signup.md), and it is not in your organization’s Azure AD directory.
+This issue can occur if the account is registered in an [unmanaged Azure AD directory](../../active-directory/users-groups-roles/directory-self-service-signup.md), and it is not in your organization's Azure AD directory.
 
-To resolve this issue, sign-up the Azure account by using another account, or take over the unmanaged AD directory. For more information, see [Take over an unmanaged directory as administrator in Azure Active Directory](../../active-directory/users-groups-roles/domains-admin-takeover.md).
+To resolve this issue, sign up the Azure account by using another account, or take over the unmanaged AD directory. For more information, see [Take over an unmanaged directory as administrator in Azure Active Directory](../../active-directory/users-groups-roles/domains-admin-takeover.md).
 
 ## Additional help resources
 

articles/cosmos-db/media/managed-identity-based-authentication/identity-tab-selection.png

@@ -1,8 +1,9 @@
 ---
 title: Troubleshoot Azure subscription sign-in issues
 description: Helps to resolve the issues in which you can't sign-in the Azure portal or Azure account center.
+services: cost-management-billing
 author: v-miegge
-ms.reviewer: dcscontentpm
+manager: dcscontentpm
 tags: billing
 ms.service: cost-management-billing
 ms.topic: conceptual
@@ -31,12 +32,12 @@ This issue can occur if you use more than one user account in an internet browse
 To resolve the issue, try one of the following methods:
 
 - Clear the cache and delete Internet cookies. In Internet Explorer, click **Tools** > **Internet Options** > **Delete**. Make sure that the check boxes for temporary files, cookies, password, and browsing history are selected, and then click Delete.
-- Reset the Internet Explorer settings to revert any personal settings that you’ve made. Click **Tools** > **Internet Options** > **Advanced** > select the **Delete personal settings** box > **Reset**.
+- Reset the Internet Explorer settings to revert any personal settings that you've made. Click **Tools** > **Internet Options** > **Advanced** > select the **Delete personal settings** box > **Reset**.
 - Use the private browsing mode for your browser. For Internet Explorer:  Click **Tools** > **Safety** > **InPrivate Browsing**, and then browse and sign-in to the [Azure portal](https://portal.azure.com/) or [Azure account center](https://account.azure.com/Subscriptions).
 
 ### I can sign-in but I see *No subscriptions found*
 
-This problem occurs if you selected at the wrong directory, or if your account doesn’t have sufficient permissions.
+This problem occurs if you selected at the wrong directory, or if your account doesn't have sufficient permissions.
 
 **Scenario 1:** Error message is received in the [Azure portal](https://portal.azure.com/)