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

Author: KumudD

articles/active-directory/b2b/current-limitations.md

@@ -24,10 +24,13 @@ With Azure AD B2B, you can enforce multi-factor authentication at the resource o
 ## Instant-on
 In the B2B collaboration flows, we add users to the directory and dynamically update them during invitation redemption, app assignment, and so on. The updates and writes ordinarily happen in one directory instance and must be replicated across all instances. Replication is completed once all instances are updated. Sometimes when the object is written or updated in one instance and the call to retrieve this object is to another instance, replication latencies can occur. If that happens, refresh or retry to help. If you are writing an app using our API, then retries with some back-off is a good, defensive practice to alleviate this issue.
 
+## Azure AD directories
+Azure AD B2B is subject to Azure AD service directory limits. For details about the number of directories a user can create and the number of directories to which a user or guest user can belong, see [Azure AD service limits and restrictions](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-service-limits-restrictions).
+
 ## Next steps
 
 See the following articles on Azure AD B2B collaboration:
 
 - [What is Azure AD B2B collaboration?](what-is-b2b.md)
-- [Delegate B2bB collaboration invitations](delegate-invitations.md)
+- [Delegate B2B collaboration invitations](delegate-invitations.md)
 

articles/active-directory/connect/active-directory-aadconnect-version-history.md

@@ -55,6 +55,7 @@ Download| [Download Azure AD Connect](http://go.microsoft.com/fwlink/?LinkId=615
 
 ### Fixed issues 
 
+- Fixed a bug where the AAD Connect server would show high CPU usage after upgrading to .Net 4.7.2
 - Fixed a bug that would intermittently produce an error message for an auto-resolved SQL deadlock issue
 - Fixed several accessibility issues for the Sync Rules Editor and the Sync Service Manager  
 - Fixed a bug where Azure AD Connect can not get registry setting information

articles/active-directory/managed-service-identity/how-to-manage-ua-identity-powershell.md

@@ -35,6 +35,12 @@ In this article, you learn how to create, list and delete a user assigned identi
     - [Managed Identity Contributor](/azure/role-based-access-control/built-in-roles#managed-identity-contributor) role to create, read (list), update, and delete a user assigned identity.
     - [Managed Identity Operator](/azure/role-based-access-control/built-in-roles#managed-identity-operator) role to read (list) the properties of a user assigned identity.
 
+> [!NOTE]
+> While user assigned identities are still in preview you need to first manually install the AzureRM.ManagedServiceIdentity module using the following command. 
+```azurepowershell-interactive
+Install-Module -Name AzureRM.ManagedServiceIdentity -AllowPrerelease
+```
+
 ## Create a user assigned identity
 
 To create a user assigned identity, use the [New-AzureRmUserAssignedIdentity](/powershell/module/azurerm.managedserviceidentity/new-azurermuserassignedidentity) command. The `ResourceGroupName` parameter specifies the resource group where to create the user assigned identity, and the `-Name` parameter specifies its name. Replace the `<RESOURCE GROUP>` and `<USER ASSIGNED IDENTITY NAME>` parameter values with your own values:

articles/application-gateway/url-route-overview.md

@@ -1,5 +1,5 @@
 ---
-title: Azure Application Gatewaty URL-based content routing overview
+title: Azure Application Gateway URL-based content routing overview
 description: This article provides an overview of the Application Gateway URL-based content routing, UrlPathMap configuration and PathBasedRouting rule.
 documentationcenter: na
 services: application-gateway

articles/application-insights/app-insights-ip-addresses.md

@@ -34,7 +34,7 @@ You need to open some outgoing ports in your server's firewall to allow the Appl
 
 | Purpose | URL | IP | Ports |
 | --- | --- | --- | --- |
-| Telemetry |dc.services.visualstudio.com<br/>dc.applicationinsights.microsoft.com |40.114.241.141<br/>104.45.136.42<br/>40.84.189.107<br/>168.63.242.221<br/>52.167.221.184<br/>52.169.64.244<br/>40.85.218.175<br/>104.211.92.54 | 443 |
+| Telemetry |dc.services.visualstudio.com<br/>dc.applicationinsights.microsoft.com |40.114.241.141<br/>104.45.136.42<br/>40.84.189.107<br/>168.63.242.221<br/>52.167.221.184<br/>52.169.64.244<br/>40.85.218.175<br/>104.211.92.54<br/>52.175.198.74 | 443 |
 | Live Metrics Stream |rt.services.visualstudio.com<br/>rt.applicationinsights.microsoft.com |23.96.28.38<br/>13.92.40.198 |443 |
 
 ## Status Monitor

articles/automation/automation-hrw-run-runbooks.md

@@ -163,10 +163,10 @@ Hybrid Runbook Workers can be configured to run only signed runbooks with some c
 
 ### Create Signing Certificate
 
-The following example creates a self signed certificate that can be used for signing runbooks. The sample creates the certificate and exports it. The certificate is imported into the Hybrid Runbook Workers later. The thumbprint is returned as well, this is used later to reference the certificate.
+The following example creates a self-signed certificate that can be used for signing runbooks. The sample creates the certificate and exports it. The certificate is imported into the Hybrid Runbook Workers later. The thumbprint is returned as well, this is used later to reference the certificate.
 
 ```powershell
-# Create a self signed runbook that can be used for code signing
+# Create a self-signed certificate that can be used for code signing
 $SigningCert = New-SelfSignedCertificate -CertStoreLocation cert:\LocalMachine\my `
                                         -Subject "CN=contoso.com" `
                                         -KeyAlgorithm RSA `
@@ -205,14 +205,14 @@ Set-HybridRunbookWorkerSignatureValidation -Enable $true -TrustedCertStoreLocati
 
 ### Sign your Runbooks using the certificate
 
-With the Hybrid Runbook workers configured to use only signed runbooks. You must sign runbooks that are to be used on the Hybrid Runbook Worker. Use the following sample PowerShell to sign your runbooks.
+With the Hybrid Runbook workers configured to use only signed runbooks, you must sign runbooks that are to be used on the Hybrid Runbook Worker. Use the following sample PowerShell to sign your runbooks.
 
 ```powershell
 $SigningCert = ( Get-ChildItem -Path cert:\LocalMachine\My\<CertificateThumbprint>)
 Set-AuthenticodeSignature .\TestRunbook.ps1 -Certificate $SigningCert
 ```
 
-Once the runbook has been signed, it must be imported into your Automation Account and published with the signature block. To learn how import runbooks, see [Importing a runbook from a file into Azure Automation](automation-creating-importing-runbook.md#importing-a-runbook-from-a-file-into-azure-automation).
+When the runbook has been signed, it must be imported into your Automation Account and published with the signature block. To learn how to import runbooks, see [Importing a runbook from a file into Azure Automation](automation-creating-importing-runbook.md#importing-a-runbook-from-a-file-into-azure-automation).
 
 ## Troubleshoot
 

articles/automation/automation-runbook-settings.md

@@ -28,7 +28,7 @@ By default, Verbose and Progress records are not written to job history. You can
 ### Changing runbook settings with the Azure portal
 You can change settings for a runbook in the Azure portal from the **Settings** blade for the runbook.
 
-1. In the Azure portal, select **Automation** and then then click the name of an automation account.
+1. In the Azure portal, select **Automation** and then click the name of an automation account.
 2. Select the **Runbooks** tab.
 3. Click the name of a runbook and you are directed to the settings blade for the runbook. From here you can specify or modify tags, the runbook description, configure logging and tracing settings, and access support tools to help you solve problems.     
 

articles/azure-functions/ip-addresses.md

@@ -35,20 +35,12 @@ Each function app has a single inbound IP address. To find that IP address:
 3. Select **Platform features**.
 4. Select **Properties**, and the inbound IP address appears under **Virtual IP address**.
 
-Under **Platform features**, an alternative way to find IP addresses is to select **Diagnose and Solve Problems > Check IP Configuration**.
-
 ## Function app outbound IP addresses
 
 Each function app has a set of available outbound IP addresses. Any outbound connection from a function, such as to a back-end database, uses one of the available outbound IP addresses as the origin IP address. You can't know beforehand which IP address a given connection will use. For this reason, your back-end service must open its firewall to all of the function app's outbound IP addresses.
 
 To find the outbound IP addresses available to a function app:
 
-1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Navigate to the function app.
-3. Select **Platform features > Diagnose and Solve Problems > Check IP Configuration**.
-
-To find the IP addresses that would be available when the function app scales to other pricing tiers:
-
 1. Sign in to the [Azure Resource Explorer](https://resources.azure.com).
 2. Select **subscriptions > {your subscription} > providers > Microsoft.Web > sites**.
 3. In the JSON panel, find the site with an `id` property that ends in the name of your function app.

articles/azure-government/TOC.md

@@ -53,6 +53,7 @@
 ### [Monitoring + Management](documentation-government-services-monitoringandmanagement.md)
 ### [Developer Tools](documentation-government-services-devtools.md)
 ## [CSP for Azure Government](documentation-government-csp-application.md)
+### [Approved resellers](documentation-government-csp-list.md)
 ## Certifications
 ### [ITAR](documentation-government-overview-itar.md)
 ### [Justice and Public Safety](documentation-government-overview-jps.md)