Merge pull request #230770 from spelluru/egridfilenames0314

remove event-grid from file names

Author: Stacyrch140

articles/connectors/managed.md

@@ -612,7 +612,7 @@ For more information, see these topics:
 [azure-automation-doc]: /connectors/azureautomation/ "Create and manage automation jobs for your cloud and on-premises infrastructure"
 [azure-blob-storage-doc]: ./connectors-create-api-azureblobstorage.md "Manage files in your blob container with Azure blob storage connector"
 [azure-cosmos-db-doc]: ./connectors-create-api-cosmos-db.md "Connect to Azure Cosmos DB so that you can access and manage Azure Cosmos DB documents"
-[azure-event-grid-doc]: ../event-grid/monitor-virtual-machine-changes-event-grid-logic-app.md "Monitor events published by an Event Grid, for example, when Azure resources or third-party resources change"
+[azure-event-grid-doc]: ../event-grid/monitor-virtual-machine-changes-logic-app.md "Monitor events published by an Event Grid, for example, when Azure resources or third-party resources change"
 [azure-event-hubs-doc]: ./connectors-create-api-azure-event-hubs.md "Connect to Azure Event Hubs so that you can receive and send events between logic app workflows and Event Hubs"
 [azure-file-storage-doc]: /connectors/azurefile/ "Connect to your Azure Storage account so that you can create, update, get, and delete files"
 [azure-key-vault-doc]: /connectors/keyvault/ "Connect to your Azure Key Vault so that you can manage your secrets and keys"

articles/event-grid/.openpublishing.redirection.event-grid.json

@@ -1,5 +1,40 @@
 {
-  "redirections": [
+  "redirections": [    
+    {
+      "source_path": "scripts/event-grid-powershell-create-custom-topic.md",
+      "redirect_url": "/azure/event-grid/scripts/powershell-create-custom-topic",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "scripts/event-grid-powershell-blob.md",
+      "redirect_url": "/azure/event-grid/scripts/powershell-blob",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "scripts/event-grid-powershell-azure-subscription.md",
+      "redirect_url": "/azure/event-grid/scripts/powershell-azure-subscription",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "scripts/event-grid-cli-subscribe-custom-topic.md",
+      "redirect_url": "/azure/event-grid/scripts/cli-subscribe-custom-topic",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "monitor-virtual-machine-changes-event-grid-logic-app.md",
+      "redirect_url": "/azure/event-grid/monitor-virtual-machine-changes-logic-app",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "event-grid-event-hubs-integration.md",
+      "redirect_url": "/azure/event-grid/event-hubs-integration",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "event-grid-faq.yml",
+      "redirect_url": "/azure/event-grid/faq",
+      "redirect_document_id": false
+    },    
     {
       "source_path": "custom-disaster-recovery.md",
       "redirect_url": "/azure/event-grid/custom-disaster-recovery-client-side",

articles/event-grid/blob-event-quickstart-portal.md

@@ -143,5 +143,5 @@ Now that you know how to create custom topics and event subscriptions, learn mor
 
 - [About Event Grid](overview.md)
 - [Route Blob storage events to a custom web endpoint](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json)
-- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-event-grid-logic-app.md)
-- [Stream big data into a data warehouse](event-grid-event-hubs-integration.md)
+- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-logic-app.md)
+- [Stream big data into a data warehouse](event-hubs-integration.md)

articles/event-grid/compare-messaging-services.md

@@ -77,7 +77,7 @@ For more information, see [Service Bus overview](../service-bus-messaging/servic
 ## Use the services together
 In some cases, you use the services side by side to fulfill distinct roles. For example, an e-commerce site can use Service Bus to process the order, Event Hubs to capture site telemetry, and Event Grid to respond to events like an item was shipped.
 
-In other cases, you link them together to form an event and data pipeline. You use Event Grid to respond to events in the other services. For an example of using Event Grid with Event Hubs to migrate data to Azure Synapse Analytics, see [Stream big data into a Azure Synapse Analytics](event-grid-event-hubs-integration.md). The following image shows the workflow for streaming the data.
+In other cases, you link them together to form an event and data pipeline. You use Event Grid to respond to events in the other services. For an example of using Event Grid with Event Hubs to migrate data to Azure Synapse Analytics, see [Stream big data into a Azure Synapse Analytics](event-hubs-integration.md). The following image shows the workflow for streaming the data.
 
 :::image type="content" source="./media/compare-messaging-services/overview.svg" alt-text="Image showing how Event Hubs, Service Bus, and Event Grid can be connected together.":::
 

articles/event-grid/concepts.md

@@ -48,7 +48,7 @@ A subscription tells Event Grid which events on a topic you're interested in rec
 
 For examples of creating subscriptions, see:
 
-* [Azure CLI samples for Event Grid](scripts/event-grid-cli-subscribe-custom-topic.md)
+* [Azure CLI samples for Event Grid](scripts/cli-subscribe-custom-topic.md)
 * [Azure PowerShell samples for Event Grid](powershell-samples.md)
 * [Azure Resource Manager templates for Event Grid](template-samples.md)
 

articles/event-grid/configure-custom-topic.md

@@ -70,7 +70,7 @@ You can use similar steps to enable an identity for an Event Grid domain.
 1. On the left menu, select **Configuration** under **Settings**.
 1. 2. For **Data residency**, select whether you don't want any data to be replicated to another region (**Regional**) or you want the metadata to be replicated to a predefined secondary region (**Cross-Geo**). 
 
-    The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./event-grid-faq.yml).
+    The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./faq.yml).
 
     If you select the **Regional** option, you may define your own disaster recovery plan. 
 

articles/event-grid/create-custom-topic.md

@@ -72,7 +72,7 @@ On the **Security** page of the **Create Topic**  or **Create Event Grid Domain*
 
     :::image type="content" source="./media/create-custom-topic/data-residency.png" alt-text="Screenshot showing the Data residency section of the Advanced page in the Create Topic wizard.":::
 
-    The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./event-grid-faq.yml).
+    The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./faq.yml).
 
     If you select the **Regional** option, you may define your own disaster recovery plan. 
 3. Select **Next: Tags** to move to the **Tags** page. 

articles/event-grid/custom-event-quickstart-portal.md

@@ -23,20 +23,20 @@ In this article, you use the Azure portal to do the following tasks:
 [!INCLUDE [event-grid-register-provider-portal.md](../../includes/event-grid-register-provider-portal.md)]
 
 ## Create a custom topic
-An event grid topic provides a user-defined endpoint that you post your events to. 
+An Event Grid topic provides a user-defined endpoint that you post your events to. 
 
 1. Sign in to [Azure portal](https://portal.azure.com/).
 2. In the search bar at the topic, type **Event Grid Topics**, and then select **Event Grid Topics** from the drop-down list. 
 
-    :::image type="content" source="./media/custom-event-quickstart-portal/select-event-grid-topics.png" alt-text="Screenshot showing the Azure port search bar to search for Event Grid Topics.":::
+    :::image type="content" source="./media/custom-event-quickstart-portal/select-event-grid-topics.png" alt-text="Screenshot showing the Azure port search bar to search for Event Grid topics.":::
 3. On the **Event Grid Topics** page, select **+ Create** on the toolbar. 
 
-    :::image type="content" source="./media/custom-event-quickstart-portal/create-topic-button.png" alt-text="Screenshot showing the Create Topic button on Event Grid Topics page.":::
+    :::image type="content" source="./media/custom-event-quickstart-portal/create-topic-button.png" alt-text="Screenshot showing the Create Topic button on Event Grid topics page.":::
 1. On the **Create Topic** page, follow these steps:
     1. Select your Azure **subscription**.
     2. Select an existing resource group or select **Create new**, and enter a **name** for the **resource group**.
     3. Provide a unique **name** for the custom topic. The topic name must be unique because it's represented by a DNS entry. Don't use the name shown in the image. Instead, create your own name - it must be between 3-50 characters and contain only values a-z, A-Z, 0-9, and "-".
-    4. Select a **location** for the event grid topic.
+    4. Select a **location** for the Event Grid topic.
     5. Select **Review + create** at the bottom of the page. 
 
         :::image type="content" source="./media/custom-event-quickstart-portal/create-custom-topic.png" alt-text="Create Topic page":::
@@ -45,19 +45,19 @@ An event grid topic provides a user-defined endpoint that you post your events t
         :::image type="content" source="./media/custom-event-quickstart-portal/review-create-page.png" alt-text="Review settings and create":::
 5. After the deployment succeeds, select **Go to resource** to navigate to the **Event Grid Topic** page for your topic. Keep this page open. You use it later in the quickstart. 
 
-    :::image type="content" source="./media/custom-event-quickstart-portal/event-grid-topic-home-page.png" alt-text="Screenshot showing the Event Grid Topic home page.":::
+    :::image type="content" source="./media/custom-event-quickstart-portal/event-grid-topic-home-page.png" alt-text="Screenshot showing the Event Grid topic home page.":::
 
     > [!NOTE]
     > To keep the quickstart simple, you'll be using only the **Basics** page to create a topic. For detailed steps about configuring network, security, and data residency settings on other pages of the wizard, see [Create a custom topic](create-custom-topic.md).
 
 ## Create a message endpoint
-Before you create a subscription for the custom topic, create an endpoint for the event message. Typically, the endpoint takes actions based on the event data. To simplify this quickstart, you deploy a [pre-built web app](https://github.com/Azure-Samples/azure-event-grid-viewer) that displays the event messages. The deployed solution includes an App Service plan, an App Service web app, and source code from GitHub.
+Before you create a subscription for the custom topic, create an endpoint for the event message. Typically, the endpoint takes actions based on the event data. To simplify this quickstart, you deploy a [prebuilt web app](https://github.com/Azure-Samples/azure-event-grid-viewer) that displays the event messages. The deployed solution includes an App Service plan, an App Service web app, and source code from GitHub.
 
 1. In the article page, select **Deploy to Azure** to deploy the solution to your subscription. In the Azure portal, provide values for the parameters.
 
    <a href="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure-Samples%2Fazure-event-grid-viewer%2Fmaster%2Fazuredeploy.json" target="_blank"><img src="../media/template-deployments/deploy-to-azure.svg"  alt="Button to deploy to Azure."></a>
 2. On the **Custom deployment** page, do the following steps: 
-    1. For **Resource group**, select the resource group that you created when creating the storage account. It will be easier for you to clean up after you are done with the tutorial by deleting the resource group.  
+    1. For **Resource group**, select the resource group that you created when creating the storage account. It will be easier for you to clean up after you're done with the tutorial by deleting the resource group.  
     2. For **Site Name**, enter a name for the web app.
     3. For **Hosting plan name**, enter a name for the App Service plan to use for hosting the web app.
     5. Select **Review + create**. 
@@ -80,7 +80,7 @@ Before you create a subscription for the custom topic, create an endpoint for th
 
 ## Subscribe to custom topic
 
-You subscribe to an event grid topic to tell Event Grid which events you want to track, and where to send the events.
+You subscribe to an Event Grid topic to tell Event Grid which events you want to track, and where to send the events.
 
 1. Now, on the **Event Grid Topic** page for your custom topic, select **+ Event Subscription** on the toolbar.
 
@@ -114,12 +114,12 @@ The first example uses Azure CLI. It gets the URL and key for the custom topic,
 1. Select **Bash** in the top-left corner of the Cloud Shell window. 
 
     ![Cloud Shell - Bash](./media/custom-event-quickstart-portal/cloud-shell-bash.png)
-1. Run the following command to get the **endpoint** for the topic: After you copy and paste the command, update the **topic name** and **resource group name** before you run the command. You'll publish sample events to this topic endpoint. 
+1. Run the following command to get the **endpoint** for the topic: After you copy and paste the command, update the **topic name** and **resource group name** before you run the command. You publish sample events to this topic endpoint. 
 
     ```azurecli
     endpoint=$(az eventgrid topic show --name <topic name> -g <resource group name> --query "endpoint" --output tsv)
     ```
-2. Run the following command to get the **key** for the custom topic: After you copy and paste the command, update the **topic name** and **resource group** name before you run the command. It's the primary key of the event grid topic. To get this key from the Azure portal, switch to the **Access keys** tab of the **Event Grid Topic** page. To be able post an event to a custom topic, you need the access key. 
+2. Run the following command to get the **key** for the custom topic: After you copy and paste the command, update the **topic name** and **resource group** name before you run the command. It's the primary key of the Event Grid topic. To get this key from the Azure portal, switch to the **Access keys** tab of the **Event Grid Topic** page. To be able post an event to a custom topic, you need the access key. 
 
     ```azurecli
     key=$(az eventgrid topic key list --name <topic name> -g <resource group name> --query "key1" --output tsv)
@@ -213,8 +213,8 @@ Now that you know how to create custom topics and event subscriptions, learn mor
 
 - [About Event Grid](overview.md)
 - [Route Blob storage events to a custom web endpoint](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json)
-- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-event-grid-logic-app.md)
-- [Stream big data into a data warehouse](event-grid-event-hubs-integration.md)
+- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-logic-app.md)
+- [Stream big data into a data warehouse](event-hubs-integration.md)
 
 See the following samples to learn about publishing events to and consuming events from Event Grid using different programming languages.