Merge pull request #95848 from MeenakshiRavi-ui/workingbranch

ktoliver · web-flow · commit f08c7cc04c4c · 2019-11-13T12:54:19.000-08:00
snippet syntax
diff --git a/articles/peering-service/azure-portal.md b/articles/peering-service/azure-portal.md
@@ -25,7 +25,8 @@ If you don't have an Azure subscription, create an [account](https://azure.micro
 > This preview version is provided without a service level agreement. We don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. 
 > For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-## Prerequisites 
+## Prerequisites
+
 You must have the following:
 
 ### Azure account
@@ -44,7 +45,7 @@ Before you proceed to the steps of registering the Peering Service, you need to
 
 **Azure PowerShell**
 
-```PowerShellCopy
+```azurepowershell-interactive
 Register-AzProviderFeature-FeatureName AllowPeeringService ProviderNamespace Microsoft.Peering 
 
 Register-AzResourceProvider -ProviderNamespace Microsoft.Peering 
@@ -53,7 +54,7 @@ Register-AzResourceProvider -ProviderNamespace Microsoft.Peering
 
 **Azure CLI**
 
-```azurecli
+```azurecli-interactive
 az feature register --namespace Microsoft.Peering--name AllowPeeringService
 ```
 
diff --git a/articles/peering-service/cli.md b/articles/peering-service/cli.md
@@ -28,6 +28,7 @@ If you choose to install and use the CLI locally, this article requires the Azur
 > For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
 ## Prerequisites 
+
 You must have the following:
 
 ### Azure account
@@ -44,7 +45,7 @@ Make sure that the connectivity providers are partnered with Microsoft.
 
 To begin your configuration, sign in to your Azure account. If you use the Cloud Shell **Try It** option, you're signed in automatically. Use the following examples to help you connect.
 
-```azurecli
+```azurecli-interactive
 az login
 ```
 
@@ -70,7 +71,7 @@ az group create -n MyResourceGroup -l "West US"
 
 Before you proceed to the steps of registering the Peering Service connection by using the Azure CLI, register your subscription with the resource provider and feature flag by using the Azure CLI. The Azure CLI commands are specified here:
 
-```azurecli
+```azurecli-interactive
 
 az feature register --namespace Microsoft.Peering --name AllowPeeringService
 
diff --git a/articles/peering-service/connection-telemetry.md b/articles/peering-service/connection-telemetry.md
@@ -22,15 +22,15 @@ Connection telemetry provides insights collected for the connectivity between th
 
 ## Preview scope
 
-Connection telemetry is composed of the following scopes: 
+Connection telemetry is composed of the following scopes:
 
-**Latency measurement**
+### Latency measurement
 
  Latency is measured from the client to the Microsoft edge PoP for the registered prefixes.
 
-**Route (prefix) monitoring and protection** 
+### Route prefix monitoring and protection
 
-Routing paths are monitored for any suspicious activity that's then captured in event logs. For instance, event logs are created for some of these factors: 
+Routing paths are monitored for any suspicious activity that's then captured in event logs. For instance, event logs are created for some of these factors:
 
 - Prefix hijacks
 - Prefix withdrawal
diff --git a/articles/peering-service/index.yml b/articles/peering-service/index.yml
@@ -28,7 +28,7 @@ landingContent:
             url: about.md
       - linkListType: concept
         links:
-          - text: Location and partners
+          - text: Locations and partners
             url: location-partners.md
           - text: Connections
             url: connection.md
diff --git a/articles/peering-service/location-partners.md b/articles/peering-service/location-partners.md
@@ -29,7 +29,7 @@ The table in this article provides information on the Peering Service connectivi
 
 | **Partners** | **Market**|
 |-----------|---------|
-| BBIX |Japan |
+| [BBIX](https://www.bbix.net/service/mpr/) |Japan |
 | [CCL](https://concepts.co.nz/news/general-news/) |Oceania |
 | [Colt](https://www.colt.net/why-colt/strategic-alliances/microsoft-partnership/)|Europe|
 | [DE-CIX](https://www.de-cix.net/microsoft)|Europe, North America |
diff --git a/articles/peering-service/powershell.md b/articles/peering-service/powershell.md
@@ -48,7 +48,7 @@ Make sure that the connectivity providers are partnered with Microsoft.
 
 Before you proceed to the steps of registering Peering Service, register your subscription with the resource provider and feature flag by using Azure PowerShell. The Azure PowerShell commands are specified here:
 
-```PowerShellCopy
+```azurepowershell-interactive
 Register-AzProviderFeature -FeatureName AllowPeeringService ProviderNamespace Microsoft.Peering 
 
 Register-AzResourceProvider -ProviderNamespace Microsoft.Peering 
@@ -61,32 +61,34 @@ Run the following commands in Azure PowerShell to acquire the location and servi
 
 Get Peering Service locations:
 
-```
+```azurepowershell-interactive
 Get-AzPeeringServiceLocation -Country "United States"
 ```
 
 Get Peering Service providers:
               
-```
+```azurepowershell-interactive
 Get-AzPeeringServiceProvider
 ```
 
 ### Register the Peering Service connection
 
 Register the Peering Service connection by using the following set of commands via Azure PowerShell. This example registers the Peering Service named myPeeringService.
 
-```loc = "Washington"
+```azurepowershell-interactive
+$loc = "Washington"
 $provider = "TestPeer1"
 $resourceGroup = "MyResourceGroup"
 $name = “myPeeringService”
-$peeringService = New-AzPeeringService -ResourceGroupName $resourceGroup -Name $name -PeeringLocation $loc -PeeringServiceProvider $provider 
+$peeringService = New-AzPeeringService -ResourceGroupName $resourceGroup -Name $name -PeeringLocation $loc -PeeringServiceProvider $provider
 ```
 
 ### Register the Peering Service prefix
 
 Register the prefix that's provided by the connectivity provider by executing the following commands via Azure PowerShell. This example registers the prefix named myPrefix.
 
-```$loc = "Washington"
+```azurepowershell-interactive
+$loc = "Washington"
 $provider = "TestPeer1"
 $resourceGroup = "MyResourceGroup"
 $name = “myPeeringService”
@@ -100,27 +102,27 @@ $prefixService = $peeringService | New-AzPeeringServicePrefix -Name $prefixName
 
 To view the list of all Peering Services connections, run the following command:
 
-```
+```azurepowershell-interactive
 $peeringService = Get-AzPeeringService
 ```
 
 ### List all the Peering Service prefixes
 
 To view the list of all Peering Service prefixes, run the following command:
 
-```
+```azurepowershell-interactive
  $prefixName = "myPrefix"
 ```
 
-```
+```azurepowershell-interactive
 $prefix = Get-AzPeeringServicePrefix -PeeringServiceName "myPeeringService" -ResourceGroupName "MyResourceGroup" -Name "myPrefix"
 ```
 
 ### Remove the Peering Service prefix
 
 To remove the Peering Service prefix, run the following command:
 
-```
+```azurepowershell-interactive
 Remove-AzPeeringServicePrefix -ResourceGroupName  "MyResourceGroup" -Name "myPrefix" -PeeringServiceName "myPeeringService"
 ```
 
