content cleanup: OPS-build-warnings-jo-batch2

Author: jomolnar

articles/active-directory-domain-services/active-directory-ds-troubleshooting.md

@@ -75,8 +75,8 @@ Use the following PowerShell script to find the application and delete it.
 
 > [!NOTE]
 > This script uses **Azure AD PowerShell version 2** cmdlets. For a full list of all available cmdlets and to download the module, read the [AzureAD PowerShell reference documentation](https://msdn.microsoft.com/library/azure/mt757189.aspx).
-> 
-> 
+>
+>
 
 ```
 $InformationPreference = "Continue"
@@ -129,18 +129,18 @@ If one or more users in your Azure AD tenant are unable to sign in to the newly
 
 > [!NOTE]
 > We recommend using the UPN format to sign in to the Azure AD Domain Services managed domain.
-> 
-> 
+>
+>
 
 * Ensure that you have [enabled password synchronization](active-directory-ds-getting-started-password-sync.md) in accordance with the steps outlined in the Getting Started guide.
 * **External accounts:** Ensure that the affected user account is not an external account in the Azure AD tenant. Examples of external accounts include Microsoft accounts (for example, '[email protected]') or user accounts from an external Azure AD directory. Since Azure AD Domain Services does not have credentials for such user accounts, these users cannot sign in to the managed domain.
 * **Synced accounts:** If the affected user accounts are synchronized from an on-premises directory, verify that:
-  
-  * You have deployed or updated to the [latest recommended release of Azure AD Connect](active-directory-ds-getting-started-password-sync.md#install-or-update-azure-ad-connect).
+
+  * You have deployed or updated to the [latest recommended release of Azure AD Connect](https://www.microsoft.com/en-us/download/details.aspx?id=47594).
   * You have configured Azure AD Connect to [perform a full synchronization](active-directory-ds-getting-started-password-sync.md).
   * Depending on the size of your directory, it may take a while for user accounts and credential hashes to be available in Azure AD Domain Services. Ensure you wait long enough before retrying authentication (depending on the size of your directory - a few hours to a day or two for large directories).
   * If the issue persists after verifying the preceding steps, try restarting the Microsoft Azure AD Sync Service. From your sync machine, launch a command prompt and execute the following commands:
-    
+
     1. net stop 'Microsoft Azure AD Sync'
     2. net start 'Microsoft Azure AD Sync'
 * **Cloud-only accounts**: If the affected user account is a cloud-only user account, ensure that the user has changed their password after you enabled Azure AD Domain Services. This step causes the credential hashes required for Azure AD Domain Services to be generated.
@@ -152,4 +152,3 @@ To remove the user account fully from your managed domain, delete the user perma
 
 ## Contact Us
 Contact the Azure Active Directory Domain Services product team to [share feedback or for support](active-directory-ds-contact-us.md).
-

articles/api-management/api-management-howto-disaster-recovery-backup-restore.md

@@ -26,16 +26,16 @@ This guide shows how to authenticate Azure Resource Manager requests, and how to
 
 > [!NOTE]
 > The process for backing up and restoring an API Management service instance for disaster recovery can also be used for replicating API Management service instances for scenarios such as staging.
-> 
+>
 > Note that each backup expires after 7 days. If you attempt to restore a backup after the 7 day expiration period has expired, the restore will fail with a `Cannot restore: backup expired` message.
-> 
-> 
+>
+>
 
 ## Authenticating Azure Resource Manager requests
 > [!IMPORTANT]
 > The REST API for backup and restore uses Azure Resource Manager and has a different authentication mechanism than the REST APIs for managing your API Management entities. The steps in this section describe how to authenticate Azure Resource Manager requests. For more information, see [Authenticating Azure Resource Manager requests](http://msdn.microsoft.com/library/azure/dn790557.aspx).
-> 
-> 
+>
+>
 
 All of the tasks that you do on resources using the Azure Resource Manager must be authenticated with Azure Active Directory using the following steps.
 
@@ -46,9 +46,9 @@ All of the tasks that you do on resources using the Azure Resource Manager must
 The first step is to create an Azure Active Directory application. Log into the [Azure Classic Portal](http://manage.windowsazure.com/) using the subscription that contains your API Management service instance and navigate to the **Applications** tab for your default Azure Active Directory.
 
 > [!NOTE]
-> If the Azure Active Directory default directory is not visible to your account, contact the administrator of the Azure subscription to grant the required permissions to your account. For information on locating your default directory, see [Locate your default directory](../virtual-machines/virtual-machines-windows-create-aad-work-id.md#locate-your-default-directory-in-the-azure-portal).
-> 
-> 
+> If the Azure Active Directory default directory is not visible to your account, contact the administrator of the Azure subscription to grant the required permissions to your account. For information on locating your default directory, see "Locate your default directory in the Azure classic portal" in [Creating a Work or School identity in Azure Active Directory to use with Windows VMs](../virtual-machines/virtual-machines-windows-create-aad-work-id.md).
+>
+>
 
 ![Create Azure Active Directory application][api-management-add-aad-application]
 
@@ -99,7 +99,7 @@ Replace `{tenant id}` with the tenant id of the Azure Active Directory applicati
 
 ![Endpoints][api-management-endpoint]
 
-Replace `{application id}` and `{redirect uri}` using the **Client Id** and  the URL from the **Redirect Uris** section from your Azure Active Directory application's **Configure** tab. 
+Replace `{application id}` and `{redirect uri}` using the **Client Id** and  the URL from the **Redirect Uris** section from your Azure Active Directory application's **Configure** tab.
 
 ![Resources][api-management-aad-resources]
 
@@ -139,8 +139,8 @@ Backup is a long running operation that may take multiple minutes to complete.
 **Note**:
 
 * **Container** specified in the request body **must exist**.
-* While backup is in progress you **should not attempt any service management operations** such as SKU upgrade or downgrade, domain name change, etc. 
-* Restore of a **backup is guaranteed only for 7 days** since the moment of its creation. 
+* While backup is in progress you **should not attempt any service management operations** such as SKU upgrade or downgrade, domain name change, etc.
+* Restore of a **backup is guaranteed only for 7 days** since the moment of its creation.
 * **Usage data** used for creating analytics reports **is not included** in the backup. Use [Azure API Management REST API][Azure API Management REST API] to periodically retrieve analytics reports for safekeeping.
 * The frequency with which you perform service backups will affect your recovery point objective. To minimize it we advise implementing regular backups as well as performing on-demand backups after making important changes to your API Management service.
 * **Changes** made to the service configuration (e.g. APIs, policies, developer portal appearance) while backup operation is in process **might not be included in the backup and therefore will be lost**.
@@ -172,15 +172,15 @@ Restore is a long running operation that may take up to 30 or more minutes to co
 
 > [!IMPORTANT]
 > **The SKU** of the service being restored into **must match** the SKU of the backed up service being restored.
-> 
+>
 > **Changes** made to the service configuration (e.g. APIs, policies, developer portal appearance) while restore operation is in progress **could be overwritten**.
-> 
-> 
+>
+>
 
 ## Next steps
 Check out the following Microsoft blogs for two different walkthroughs of the backup/restore process.
 
-* [Replicate Azure API Management Accounts](https://www.returngis.net/en/2015/06/replicate-azure-api-management-accounts/) 
+* [Replicate Azure API Management Accounts](https://www.returngis.net/en/2015/06/replicate-azure-api-management-accounts/)
   * Thank you to Gisela for her contribution to this article.
 * [Azure API Management: Backing Up and Restoring Configuration](http://blogs.msdn.com/b/stuartleeks/archive/2015/04/29/azure-api-management-backing-up-and-restoring-configuration.aspx)
   * The approach detailed by Stuart does not match the official guidance but it is very interesting.
@@ -200,4 +200,3 @@ Check out the following Microsoft blogs for two different walkthroughs of the ba
 [api-management-aad-resources]: ./media/api-management-howto-disaster-recovery-backup-restore/api-management-aad-resources.png
 [api-management-arm-token]: ./media/api-management-howto-disaster-recovery-backup-restore/api-management-arm-token.png
 [api-management-endpoint]: ./media/api-management-howto-disaster-recovery-backup-restore/api-management-endpoint.png
-

articles/application-gateway/application-gateway-introduction.md

@@ -57,7 +57,7 @@ Application Gateway is currently offered in three sizes: Small, Medium, and Larg
 
 There are currently two skus for Application Gateway: WAF and Standard.
 
-You can create up to 50 application gateways per subscription, and each application gateway can have up to 10 instances each. Each application gateway can consist of 20 http listeners. For a complete list of application gateway limits visit the [Service Limits](../azure-subscription-service-limits.md#application-gateway) page.
+You can create up to 50 application gateways per subscription, and each application gateway can have up to 10 instances each. Each application gateway can consist of 20 http listeners. For a complete list of application gateway limits, see [Azure subscription and service limits, quotas, and constraints](../azure-subscription-service-limits.md).
 
 The following table shows an average performance throughput for each application gateway instance:
 
@@ -68,8 +68,8 @@ The following table shows an average performance throughput for each application
 
 > [!NOTE]
 > These values are approximate values for an application gateway throughput. The actual throughput depends on various environment details, such as average page size, location of back-end instances, and processing time to serve a page. For exact performance numbers, you should run your own tests, these values are only provided for capacity planning guidance.
-> 
-> 
+>
+>
 
 ## Health monitoring
 Azure Application Gateway automatically monitors the health of the back-end instances through basic or custom health probes. By using health probes, this ensures that only healthy hosts respond to traffic. For more information, see [Application Gateway health monitoring overview](application-gateway-probe-overview.md).
@@ -83,4 +83,3 @@ You can create and manage an application gateway by using REST APIs, PowerShell
 After learning about Application gateway, you can [create an application gateway](application-gateway-create-gateway-portal.md) or you can [create an application gateway SSL offload](application-gateway-ssl-arm.md) to load-balance HTTPS connections.
 
 To learn how to create an application gateway using URL-based content routing, go to [Create an application gateway using URL-based routing](application-gateway-create-url-route-arm-ps.md) for more information.
-