more files

Author: v-thepet

articles/event-grid/how-to-filter-events.md

@@ -189,7 +189,7 @@ These examples create a custom topic. They subscribe to the custom topic and fil
 
 For Azure CLI, use:
 
-```azurecli-interactive
+```azurecli
 topicName=<your-topic-name>
 endpointURL=<endpoint-URL>
 
@@ -210,7 +210,7 @@ Notice that an [expiration date](concepts.md#event-subscription-expiration) is s
 
 For PowerShell, use:
 
-```azurepowershell-interactive
+```powershell
 $topicName = <your-topic-name>
 $endpointURL = <endpoint-URL>
 
@@ -236,7 +236,7 @@ To test the filter, send an event with the color field set to green. Because gre
 
 For Azure CLI, use:
 
-```azurecli-interactive
+```azurecli
 topicEndpoint=$(az eventgrid topic show --name $topicName -g gridResourceGroup --query "endpoint" --output tsv)
 key=$(az eventgrid topic key list --name $topicName -g gridResourceGroup --query "key1" --output tsv)
 
@@ -247,7 +247,7 @@ curl -X POST -H "aeg-sas-key: $key" -d "$event" $topicEndpoint
 
 For PowerShell, use:
 
-```azurepowershell-interactive
+```powershell
 $endpoint = (Get-AzEventGridTopic -ResourceGroupName gridResourceGroup -Name $topicName).Endpoint
 $keys = Get-AzEventGridTopicKey -ResourceGroupName gridResourceGroup -Name $topicName
 
@@ -275,14 +275,14 @@ To test a scenario where the event isn't sent, send an event with the color fiel
 
 For Azure CLI, use:
 
-```azurecli-interactive
+```azurecli
 event='[ {"id": "'"$RANDOM"'", "eventType": "recordInserted", "subject": "myapp/vehicles/cars", "eventTime": "'`date +%Y-%m-%dT%H:%M:%S%z`'", "data":{ "model": "SUV", "color": "yellow"},"dataVersion": "1.0"} ]'
 
 curl -X POST -H "aeg-sas-key: $key" -d "$event" $topicEndpoint
 ```
 For PowerShell, use:
 
-```azurepowershell-interactive
+```powershell
 $htbody = @{
     id= $eventID
     eventType="recordInserted"

articles/event-grid/resize-images-on-storage-blob-upload-event.md

@@ -53,18 +53,18 @@ You must have completed the previous Blob storage tutorial: [Upload image data i
 
 [!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
 
-If you've not previously registered the Event Grid resource provider in your subscription, make sure it's registered.
-
-```azurecli-interactive
-az provider register --namespace Microsoft.EventGrid
-```
-
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 
 If you choose to install and use the CLI locally, this tutorial requires the Azure CLI version 2.0.14 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI]( /cli/azure/install-azure-cli). 
 
 If you are not using Cloud Shell, you must first sign in using `az login`.
 
+If you've not previously registered the Event Grid resource provider in your subscription, make sure it's registered.
+
+```azurecli-interactive
+az provider register --namespace Microsoft.EventGrid
+```
+
 ## Create an Azure Storage account
 
 Azure Functions requires a general storage account. In addition to the Blob storage account you created in the previous tutorial, create a separate general storage account in the resource group by using the [az storage account create](/cli/azure/storage/account) command. Storage account names must be between 3 and 24 characters in length and may contain numbers and lowercase letters only. 

articles/event-hubs/event-hubs-resource-manager-namespace-event-hub-enable-capture.md

@@ -411,17 +411,13 @@ New-AzResourceGroupDeployment -ResourceGroupName \<resource-group-name\> -Templa
 Azure Blob Storage as destination:
 
 ```azurecli
-azure config mode arm
-
-azure group deployment create \<my-resource-group\> \<my-deployment-name\> --template-uri [https://raw.githubusercontent.com/azure/azure-quickstart-templates/master/201-eventhubs-create-namespace-and-enable-capture/azuredeploy.json][]
+az group deployment create \<my-resource-group\> \<my-deployment-name\> --template-uri [https://raw.githubusercontent.com/azure/azure-quickstart-templates/master/201-eventhubs-create-namespace-and-enable-capture/azuredeploy.json][]
 ```
 
 Azure Data Lake Store as destination:
 
 ```azurecli
-azure config mode arm
-
-azure group deployment create \<my-resource-group\> \<my-deployment-name\> --template-uri [https://raw.githubusercontent.com/azure/azure-quickstart-templates/master/201-eventhubs-create-namespace-and-enable-capture-for-adls/azuredeploy.json][]
+az group deployment create \<my-resource-group\> \<my-deployment-name\> --template-uri [https://raw.githubusercontent.com/azure/azure-quickstart-templates/master/201-eventhubs-create-namespace-and-enable-capture-for-adls/azuredeploy.json][]
 ```
 
 ## Next steps

articles/expressroute/about-public-peering.md

@@ -173,7 +173,7 @@ Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt
 
    The response is similar to the following example:
 
-   ```azurecli
+   ```output
    "allowClassicOperations": false,
    "authorizations": [],
    "circuitProvisioningState": "Enabled",
@@ -235,7 +235,7 @@ az network express-route peering show -g ExpressRouteResourceGroup --circuit-nam
 
 The output is similar to the following example:
 
-```azurecli
+```output
 {
   "azureAsn": 12076,
   "etag": "W/\"2e97be83-a684-4f29-bf3c-96191e270666\"",

articles/expressroute/expressroute-howto-expressroute-direct-cli.md

@@ -49,7 +49,7 @@ You can use Azure ExpressRoute Direct to connect directly to the Microsoft globa
 
    **Example output**
 
-   ```azurecli
+   ```output
    [
    {
     "address": "21715 Filigree Court, DC2, Building F, Ashburn, VA 20147",
@@ -116,7 +116,7 @@ You can use Azure ExpressRoute Direct to connect directly to the Microsoft globa
 
    **Example output**
 
-   ```azurecli
+   ```output
    {
    "address": "21715 Filigree Court, DC2, Building F, Ashburn, VA 20147",
    "availableBandwidths": [
@@ -154,7 +154,7 @@ You can use Azure ExpressRoute Direct to connect directly to the Microsoft globa
 
    **Example output**
 
-   ```azurecli
+   ```output
    {
    "allocationDate": "Wednesday, October 17, 2018",
    "bandwidthInGbps": 100,
@@ -222,7 +222,7 @@ Use this process to conduct a layer 1 test. Ensure that each cross-connection is
    ```
    **Example output**
 
-   ```azurecli
+   ```output
    {
    "allocationDate": "Wednesday, October 17, 2018",
    "bandwidthInGbps": 100,
@@ -295,7 +295,7 @@ Create a circuit on the ExpressRoute Direct resource:
 
   **Example output**
 
-  ```azurecli
+  ```output
   {
   "allowClassicOperations": false,
   "allowGlobalReach": false,

articles/expressroute/expressroute-howto-set-global-reach-cli.md

@@ -65,7 +65,7 @@ az network express-route peering connection create -g <ResourceGroupName> --circ
 
 The CLI output looks like this:
 
-```azurecli
+```output
 {
   "addressPrefix": "<__.__.__.__/29>",
   "authorizationKey": null,
@@ -101,7 +101,7 @@ If the two circuits aren't in the same Azure subscription, you need authorizatio
 
    The CLI output looks like this:
 
-   ```azurecli
+   ```output
    {
      "authorizationKey": "<authorizationKey>",
      "authorizationUseStatus": "Available",

articles/expressroute/howto-circuit-cli.md

@@ -35,7 +35,7 @@ This article describes how to create an Azure ExpressRoute circuit by using the
 
 To begin your configuration, sign in to your Azure account. If you use the CloudShell "Try It", you are signed in automatically. Use the following examples to help you connect:
 
-```azurecli
+```azurecli-interactive
 az login
 ```
 
@@ -61,7 +61,7 @@ az network express-route list-service-providers
 
 The response is similar to the following example:
 
-```azurecli
+```output
 [
   {
     "bandwidthsOffered": [
@@ -159,7 +159,7 @@ az network express-route list
 
 Your service key is listed in the *ServiceKey* field of the response.
 
-```azurecli
+```output
 "allowClassicOperations": false,
 "authorizations": [],
 "circuitProvisioningState": "Enabled",
@@ -200,21 +200,21 @@ az network express-route list -h
 
 When you create a new ExpressRoute circuit, the circuit is in the following state:
 
-```azurecli-interactive
+```output
 "serviceProviderProvisioningState": "NotProvisioned"
 "circuitProvisioningState": "Enabled"
 ```
 
 The circuit changes to the following state when the connectivity provider is in the process of enabling it for you:
 
-```azurecli-interactive
+```output
 "serviceProviderProvisioningState": "Provisioning"
 "circuitProvisioningState": "Enabled"
 ```
 
 For you to be able to use an ExpressRoute circuit, it must be in the following state:
 
-```azurecli-interactive
+```output
 "serviceProviderProvisioningState": "Provisioned"
 "circuitProvisioningState": "Enabled
 ```
@@ -229,7 +229,7 @@ az network express-route show --resource-group ExpressRouteResourceGroup --name
 
 The response is similar to the following example:
 
-```azurecli
+```output
 "allowClassicOperations": false,
 "authorizations": [],
 "circuitProvisioningState": "Enabled",

articles/expressroute/howto-linkvnet-cli.md

@@ -81,7 +81,7 @@ az network express-route auth create --circuit-name MyCircuit -g ExpressRouteRes
 
 The response contains the authorization key and status:
 
-```azurecli
+```output
 "authorizationKey": "0a7f3020-541f-4b4b-844a-5fb43472e3d7",
 "authorizationUseStatus": "Available",
 "etag": "W/\"010353d4-8955-4984-807a-585c21a22ae0\"",
@@ -119,7 +119,7 @@ az network express-route auth delete --circuit-name MyCircuit -g ExpressRouteRes
 
 The Circuit User needs the peer ID and an authorization key from the Circuit Owner. The authorization key is a GUID.
 
-```azurecli
+```powershell
 Get-AzExpressRouteCircuit -Name "MyCircuit" -ResourceGroupName "MyRG"
 ```