Merge pull request #58068 from DennisLee-DennisLee/v-dele-1387770-1

1387770: Changed first 10 files of broken internal links.

Author: Ja-Dunn

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

@@ -12,16 +12,16 @@ ms.workload: mobile
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 08/15/2018
+ms.date: 11/14/2018
 ms.author: apimpm
 ---
 # How to implement disaster recovery using service backup and restore in Azure API Management
 
-By choosing to publish and manage your APIs via Azure API Management you are taking advantage of many fault tolerance and infrastructure capabilities that you would otherwise have to design, implement, and manage. The Azure platform mitigates a large fraction of potential failures at a fraction of the cost.
+By publishing and managing your APIs via Azure API Management, you're taking advantage of fault tolerance and infrastructure capabilities that you'd otherwise design, implement, and manage manually. The Azure platform mitigates a large fraction of potential failures at a fraction of the cost.
 
-To recover from availability problems affecting the region where your API Management service is hosted, you should be ready to reconstitute your service in a different region at any time. Depending on your availability goals and recovery time objective, you might want to reserve a backup service in one or more regions and try to maintain their configuration and content in sync with the active service. The service "backup and restore" feature provides the necessary building block for implementing your disaster recovery strategy.
+To recover from availability problems that affect the region that hosts your API Management service, be ready to reconstitute your service in another region at any time. Depending on your availability and recovery time goals, you might want to reserve a backup service in one or more regions. You might also try to maintain their configuration and content in sync with the active service. The service "backup and restore" feature provides the necessary building block for implementing your disaster recovery strategy.
 
-This guide shows how to authenticate Azure Resource Manager requests, and how to back up and restore your API Management service instances.
+This guide shows how to authenticate Azure Resource Manager requests. It also shows how to back up and restore your API Management service instances.
 
 > [!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.
@@ -43,17 +43,17 @@ All of the tasks that you do on resources using the Azure Resource Manager must
 
 ### Create an Azure Active Directory application
 
-1. Sign in to the [Azure portal](https://portal.azure.com). 
+1. Sign in to the [Azure portal](https://portal.azure.com).
 2. Using the subscription that contains your API Management service instance, navigate to the **App registrations** tab in **Azure Active Directory** (Azure Active Directory > Manage/App registrations).
 
     > [!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.
+    > If the Azure Active Directory default directory isn't visible to your account, contact the administrator of the Azure subscription to grant the required permissions to your account.
 3. Click **New application registration**.
 
-    The **Create** window appears on the right. That is where you enter the AAD app relevant information.
+    The **Create** window appears on the right. That's where you enter the AAD app relevant information.
 4. Enter a name for the application.
 5. For the application type, select **Native**.
-6. Enter a placeholder URL such as `http://resources` for the **Redirect URI**, as it is a required field, but the value is not used later. Click the check box to save the application.
+6. Enter a placeholder URL such as `http://resources` for the **Redirect URI**, as it's a required field, but the value isn't used later. Click the check box to save the application.
 7. Click **Create**.
 
 ### Add an application
@@ -63,7 +63,7 @@ All of the tasks that you do on resources using the Azure Resource Manager must
 3. Click **+Add**.
 4. Press **Select an API**.
 5. Choose **Windows** **Azure Service Management API**.
-6. Press **Select**. 
+6. Press **Select**.
 
     ![Add permissions](./media/api-management-howto-disaster-recovery-backup-restore/add-app.png)
 
@@ -73,7 +73,7 @@ All of the tasks that you do on resources using the Azure Resource Manager must
 
 ### Configuring your app
 
-Prior to invoking the APIs that generate the backup and restore it, it is necessary to get a token. The following example uses the [Microsoft.IdentityModel.Clients.ActiveDirectory](https://www.nuget.org/packages/Microsoft.IdentityModel.Clients.ActiveDirectory) NuGet package to retrieve the token.
+Before calling the APIs that generate the backup and restore it, you need to get a token. The following example uses the [Microsoft.IdentityModel.Clients.ActiveDirectory](https://www.nuget.org/packages/Microsoft.IdentityModel.Clients.ActiveDirectory) NuGet package to retrieve the token.
 
 ```csharp
 using Microsoft.IdentityModel.Clients.ActiveDirectory;
@@ -100,9 +100,9 @@ namespace GetTokenResourceManagerRequests
 }
 ```
 
-Replace `{tentand id}`, `{application id}`, and `{redirect uri}` using the following instructions:
+Replace `{tenant id}`, `{application id}`, and `{redirect uri}` using the following instructions:
 
-1. Replace `{tenant id}` with the tenant id of the Azure Active Directory application you created. You can access the id by clicking **App registrations** -> **Endpoints**.
+1. Replace `{tenant id}` with the tenant ID of the Azure Active Directory application you created. You can access the ID by clicking **App registrations** -> **Endpoints**.
 
     ![Endpoints][api-management-endpoint]
 2. Replace `{application id}` with the value you get by navigating to the **Settings** page.
@@ -117,7 +117,7 @@ Replace `{tentand id}`, `{application id}`, and `{redirect uri}` using the follo
 
 ## Calling the backup and restore operations
 
-The REST APIs are [Api Management Service - Backup](https://docs.microsoft.com/rest/api/apimanagement/apimanagementservice/apimanagementservice_backup) and [Api Management Service - Restore](https://docs.microsoft.com/rest/api/apimanagement/apimanagementservice/apimanagementservice_restore).
+The REST APIs are [Api Management Service - Backup](/rest/api/apimanagement/apimanagementservice/backup) and [Api Management Service - Restore](/rest/api/apimanagement/apimanagementservice/restore).
 
 Before calling the "backup and restore" operations described in the following sections, set the authorization request header for your REST call.
 
@@ -126,22 +126,22 @@ request.Headers.Add(HttpRequestHeader.Authorization, "Bearer " + token);
 ```
 
 ### <a name="step1"> </a>Back up an API Management service
+
 To back up an API Management service issue the following HTTP request:
 
-```
+```http
 POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/backup?api-version={api-version}
 ```
 
 where:
 
-* `subscriptionId` - id of the subscription containing the API Management service you are attempting to back up
+* `subscriptionId` - ID of the subscription that holds the API Management service you're trying to back up
 * `resourceGroupName` - name of the resource group of your Azure API Management service
-* `serviceName` - the name of the API Management service you are making a backup of specified at the time of its creation
+* `serviceName` - the name of the API Management service you're making a backup of specified at the time of its creation
 * `api-version` - replace  with `2018-06-01-preview`
 
 In the body of the request, specify the target Azure storage account name, access key, blob container name, and backup name:
 
-
 ```json
 {
   "storageAccount": "{storage account name for the backup}",
@@ -153,32 +153,33 @@ In the body of the request, specify the target Azure storage account name, acces
 
 Set the value of the `Content-Type` request header to `application/json`.
 
-Backup is a long running operation that may take multiple minutes to complete.  If the request was successful and the backup process was initiated, you receive a `202 Accepted` response status code with a `Location` header.  Make 'GET' requests to the URL in the `Location` header to find out the status of the operation. While the backup is in progress, you continue to receive a '202 Accepted' status code. A Response code of `200 OK` indicates successful completion of the backup operation.
+Backup is a long running operation that may take more than a minute to complete.  If the request succeeded and the backup process began, you receive a `202 Accepted` response status code with a `Location` header.  Make 'GET' requests to the URL in the `Location` header to find out the status of the operation. While the backup is in progress, you continue to receive a '202 Accepted' status code. A Response code of `200 OK` indicates successful completion of the backup operation.
 
-Note the following constraints when making a backup request.
+Note the following constraints when making a backup request:
 
 * **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.
+* While backup is in progress, **avoid changes in service management** such as SKU upgrade or downgrade, change in domain name, and more.
 * Restore of a **backup is guaranteed only for 30 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 affect your recovery point objective. To minimize it, the recommendation is 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 (for example, APIs, policies, developer portal appearance) while backup operation is in process **might not be included in the backup and therefore will be lost**.
+* **Usage data** used for creating analytics reports **isn't 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 affect your recovery point objective. To minimize it, we recommend implementing regular backups and performing on-demand backups after you make changes to your API Management service.
+* **Changes** made to the service configuration, (for example, APIs, policies, and developer portal appearance) while backup operation is in process **might be excluded from the backup and will be lost**.
 
 ### <a name="step2"> </a>Restore an API Management service
-To restore an API Management service from a previously created backup make the following HTTP request:
 
-```
+To restore an API Management service from a previously created backup, make the following HTTP request:
+
+```http
 POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/restore?api-version={api-version}
 ```
 
 where:
 
-* `subscriptionId` - id of the subscription containing the API Management service you are restoring a backup into
-* `resourceGroupName` - name of the resource group containing the Azure API Management service you are restoring a backup into
-* `serviceName` - the name of the API Management service being restored into specified at the time of its creation
+* `subscriptionId` - ID of the subscription that holds the API Management service you're restoring a backup into
+* `resourceGroupName` - name of the resource group that holds the Azure API Management service you're restoring a backup into
+* `serviceName` - the name of the API Management service being restored into specified at its creation time
 * `api-version` - replace  with `2018-06-01-preview`
 
-In the body of the request, specify the backup file location, that is, Azure storage account name, access key, blob container name, and backup name:
+In the body of the request, specify the backup file location. That is, add the Azure storage account name, access key, blob container name, and backup name:
 
 ```json
 {
@@ -191,13 +192,15 @@ In the body of the request, specify the backup file location, that is, Azure sto
 
 Set the value of the `Content-Type` request header to `application/json`.
 
-Restore is a long running operation that may take up to 30 or more minutes to complete. If the request was successful and the restore process was initiated, you receive a `202 Accepted` response status code with a `Location` header. Make 'GET' requests to the URL in the `Location` header to find out the status of the operation. While the restore is in progress, you continue to receive '202 Accepted' status code. A response code of `200 OK` indicates successful completion of the restore operation.
+Restore is a long running operation that may take up to 30 or more minutes to complete. If the request succeeded and the restore process began, you receive a `202 Accepted` response status code with a `Location` header. Make 'GET' requests to the URL in the `Location` header to find out the status of the operation. While the restore is in progress, you continue to receive '202 Accepted' status code. A response code of `200 OK` indicates successful completion of the restore operation.
 
 > [!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 (for example, APIs, policies, developer portal appearance) while restore operation is in progress **could be overwritten**.
 
+<!-- Dummy comment added to suppress markdown lint warning -->
+
 > [!NOTE]
 > Backup and restore operations can also be performed with PowerShell *Backup-AzureRmApiManagement* and *Restore-AzureRmApiManagement* commands respectively.
 

articles/azure-maps/map-search-location.md

@@ -26,7 +26,7 @@ The first block of code constructs a map object and initializes the client servi
 
 The second block of code uses the [Azure Maps Fuzzy Search API](https://docs.microsoft.com/rest/api/maps/search/getsearchfuzzy) to search for point of interest. Fuzzy search API can handle any combination of fuzzy inputs. The response from the fuzzy search service is then parsed into GeoJSON format using the [getGeoJsonSearchResponse](https://docs.microsoft.com/javascript/api/azure-maps-rest/atlas.service.geojson.geojsonsearchresponse?view=azure-iot-typescript-latest#geojsonsearchresponse) method. The pins are then added to the map to show the points of interest on the map.
 
-The last block of code adjusts the camera bounds for the map by using the Map's [setCameraBounds](https://docs.microsoft.com/javascript/api/azure-maps-control/models.cameraboundsoptions?view=azure-iot-typescript-latest) property.
+The last block of code adjusts the camera bounds for the map by using the Map's [setCameraBounds](/javascript/api/azure-maps-control/atlas.map#setcamerabounds-cameraboundsoptions-) property.
 
 ## Make a search request via XMLHttpRequest
 
@@ -39,7 +39,7 @@ The second code block adds search results layer to the map. The search results l
 
 The third block of code sends an [XMLHttpRequest](https://xhr.spec.whatwg.org/) to [Azure Maps Fuzzy search API](https://docs.microsoft.com/rest/api/maps/search/getsearchfuzzy) to search for the point of interest. Fuzzy search API can handle any combination of fuzzy inputs.
 
-The last block of code parses the response and adjusts the adjusts the camera bounds for the map by using the Map's [setCameraBounds](https://docs.microsoft.com/javascript/api/azure-maps-control/models.cameraboundsoptions?view=azure-iot-typescript-latest) to render the result pins.
+The last block of code parses the response and adjusts the adjusts the camera bounds for the map by using the Map's [setCameraBounds](/javascript/api/azure-maps-control/atlas.map#setcamerabounds-cameraboundsoptions-) to render the result pins.
 
 ## Next steps
 
@@ -57,6 +57,6 @@ See the following articles for full code examples:
 
 > [!div class="nextstepaction"]
 > [Get information from a coordinate](./map-get-information-from-coordinate.md)
-
+<!-- Comment added to suppress false positive warning -->
 > [!div class="nextstepaction"]
 > [Show directions from A to B](./map-route.md)