Skip to content

Commit fa2860e

Browse files
committed
edit
1 parent de3ad6c commit fa2860e

File tree

6 files changed

+344
-9
lines changed

6 files changed

+344
-9
lines changed

articles/operational-excellence/TOC.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,14 @@
4848
href: ../mysql/howto-move-regions-portal.md?toc=/azure/operational-excellence/toc.json
4949
- name: Azure Database for PostgreSQL
5050
href: relocation-postgresql-flexible-server.md
51+
- name: Azure Event Grid
52+
items:
53+
- name: Relocate Azure Event Grid domains
54+
href: relocation-event-grid-domains.md
55+
- name: Relocate Azure Event Grid custom topics
56+
href: relocation-event-grid-custome-topics.md
57+
- name: Relocate Azure Event Grid system topics
58+
href: relocation-event-grid-system-topics.md
5159
- name: Azure Functions
5260
href: ../azure-functions/functions-move-across-regions.md?toc=/azure/operational-excellence/toc.json
5361
- name: Azure Logic apps

articles/operational-excellence/overview-relocation.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,9 @@ The following tables provide links to each Azure service relocation document. Th
6565
[Azure Database for MariaDB Server](../mariadb/howto-move-regions-portal.md?toc=/azure/operational-excellence/toc.json)|✅ | ✅| ❌ |
6666
[Azure Database for MySQL Server](../mysql/howto-move-regions-portal.md?toc=/azure/operational-excellence/toc.json)✅ | ✅| ❌ |
6767
[Azure Database for PostgreSQL](./relocation-postgresql-flexible-server.md)| ✅ | ✅| ❌ |
68+
[Azure Event Grid domains](relocation-event-grid-domains.md)| ✅ | ❌| ❌ |
69+
[Azure Event Grid custom topics](relocation-event-grid-custome-topics.md)| ✅ | ❌| ❌ |
70+
[Azure Event Grid system topics](relocation-event-grid-system-topics.md)| ✅ | ❌| ❌ |
6871
[Azure Functions](../azure-functions/functions-move-across-regions.md?toc=/azure/operational-excellence/toc.json)|✅ |❌ | ❌ |
6972
[Azure Logic apps](../logic-apps/move-logic-app-resources.md?toc=/azure/operational-excellence/toc.json)| ✅| ❌ | ❌ |
7073
[Azure Monitor - Log Analytics](./relocation-log-analytics.md)| ✅| ❌ | ❌ |

articles/operational-excellence/relocation-app-gateway.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,6 @@ ms.custom:
1616

1717
This article covers the recommended approach, guidelines, and practices to relocate Application Gateway and WAF between Azure regions.
1818

19-
20-
2119
>[!IMPORTANT]
2220
>The redeployment steps in this document apply only to the application gateway itself and not the backend services to which the application gateway rules are routing traffic.
2321
@@ -38,12 +36,10 @@ ms.custom:
3836

3937
- Ensure that the Application Gateway subnet at the target location has enough address space to accommodate the number of instances required to serve your maximum expected traffic.
4038

41-
4239
## Redeploy
4340

4441
To relocate Application Gateway and optional WAF, you must create a separate Application Gateway deployment with a new public IP address at the target location. Workloads are then migrated from the source Application Gateway setup to the new one. Since you're changing the public IP address, changes to DNS configuration, virtual networks, and subnets are also required.
4542

46-
4743
If you only want to relocate in order to gain availability zones support, see [Migrate Application Gateway and WAF to availability zone support](../reliability/migrate-app-gateway-v2.md).
4844

4945
**To create a separate Application Gateway, WAF (optional) and IP address:**
@@ -56,21 +52,20 @@ If you only want to relocate in order to gain availability zones support, see [M
5652

5753
1. Confirm that the backend pool server or service, such as VM, Virtual Machine Scale Sets, PaaS, is relocated *before* you relocate.
5854

59-
2. Create an Application Gateway and configure a new Frontend Public IP Address for the virtual network:
55+
1. Create an Application Gateway and configure a new Frontend Public IP Address for the virtual network:
6056
- Without WAF: [Create an application gateway](../application-gateway/quick-create-portal.md#create-an-application-gateway).
6157
- With WAF: [Create an application gateway with a Web Application Firewall](../web-application-firewall/ag/application-gateway-web-application-firewall-portal.md)
6258

63-
6459
1. If you have a WAF config or custom rules-only WAF Policy, [transition it to to a full WAF policy](../web-application-firewall/ag/migrate-policy.md).
6560

6661
1. If you use a zero-trust network (source region) for web applications with Azure Firewall and Application Gateway, follow the guidelines and strategies in [Zero-trust network for web applications with Azure Firewall and Application Gateway](/azure/architecture/example-scenario/gateway/application-gateway-before-azure-firewall).
6762

6863
1. Verify that the Application Gateway and WAF are working as intended.
6964

7065
1. Migrate your configuration to the new public IP address.
71-
1. Switch Public and Private endpoints in order to point to the new application gateway.
72-
1. Migrate your DNS configuration to the new Public- and/or Private IP address.
73-
1. Update endpoints in consumer applications/services. Consumer application/services updates are usually done by means of a properties change and redeployment. However, perform this method whenever a new hostname is used in respect to deployment in the old region.
66+
1. Switch Public and Private endpoints in order to point to the new application gateway.
67+
1. Migrate your DNS configuration to the new Public- and/or Private IP address.
68+
1. Update endpoints in consumer applications/services. Consumer application/services updates are usually done by means of a properties change and redeployment. However, perform this method whenever a new hostname is used in respect to deployment in the old region.
7469

7570
1. Delete the source Application Gateway and WAF resources.
7671

Lines changed: 107 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,107 @@
1+
---
2+
title: Move Azure Event Grid custom topics to another region
3+
description: This article shows you how to move Azure Event Grid custom topics from one region to another region.
4+
ms.topic: how-to
5+
ms.custom: subject-moving-resources
6+
ms.date: 08/28/2020
7+
#Customer intent: As an Azure service administrator, I want to be able to move Event Grid custom topics from one region to another region to have it closer to customers, to meet internal policy and governance requirements, or in response to capacity planning requirements.
8+
---
9+
10+
# Move Azure Event Grid custom topics to another region
11+
You might want to move your resources to another region for a number of reasons. For example, to take advantage of a new Azure region, to meet internal policy and governance requirements, or in response to capacity planning requirements.
12+
13+
Here are the high-level steps covered in this article:
14+
15+
- **Export the custom topic** resource to an Azure Resource Manager template.
16+
17+
> [!IMPORTANT]
18+
> Only the custom topic is exported to the template. Any subscriptions for the topic aren't exported.
19+
- **Use the template to deploy the custom topic** to the target region.
20+
- **Create subscriptions manually** in the target region. When you exported the custom topic to a template in the current region, only the topic is exported. Subscriptions aren't included in the template, so create them manually after the custom topic is created in the target region.
21+
- **Verify the deployment**. Verify that the custom topic is created in the target region.
22+
- To **complete the move**, delete custom topic from the source region.
23+
24+
## Prerequisites
25+
- Complete the [Quickstart: Route custom events to web endpoint](custom-event-quickstart-portal.md) in the source region. Do this step so that you can test steps in this article.
26+
- Ensure that the Event Grid service is available in the target region. See [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=event-grid&regions=all).
27+
28+
## Prepare
29+
To get started, export a Resource Manager template for the custom topic.
30+
31+
1. Sign in to the [Azure portal](https://portal.azure.com).
32+
2. In the search bar, type **Event Grid topics**, and select **Event Grid Topics** from the results list.
33+
34+
:::image type="content" source="./media/move-custom-topics-across-regions/search-topics.png" alt-text="Search for and select Event Grid topics":::
35+
3. Select the **topic** that you want to export to a Resource Manager template.
36+
37+
:::image type="content" source="./media/move-custom-topics-across-regions/select-custom-topic.png" alt-text="Select the custom topic":::
38+
4. On the **Event Grid Topic** page, select **Export Template** under **Settings** on the left menu, and then select **Download** on the toolbar.
39+
40+
:::image type="content" source="./media/move-custom-topics-across-regions/export-template-download.png" alt-text="Export template -> Download":::
41+
42+
> [!IMPORTANT]
43+
> Only the topic is exported to the template. Subscriptions for the topic aren't exported. So, you need to create subscriptions for the topic after you move the topic to the target region.
44+
5. Locate the **.zip** file you downloaded from the portal, and unzip that file to a folder of your choice. This zip file contains template and parameters JSON files.
45+
1. Open the **template.json** in an editor of your choice.
46+
8. Update `location` for the **topic** resource to the target region or location. To obtain location codes, see [Azure locations](https://azure.microsoft.com/global-infrastructure/locations/). The code for a region is the region name with no spaces, for example, `West US` is equal to `westus`.
47+
48+
```json
49+
"type": "Microsoft.EventGrid/topics",
50+
"apiVersion": "2020-06-01",
51+
"name": "[parameters('topics_mytopic0130_name')]",
52+
"location": "westus"
53+
```
54+
1. **Save** the template.
55+
56+
## Recreate
57+
Deploy the template to create a custom topic in the target region.
58+
59+
1. In the Azure portal, select **Create a resource**.
60+
2. In **Search the Marketplace**, type **template deployment**, and then press **ENTER**.
61+
3. Select **Template deployment**.
62+
4. Select **Create**.
63+
5. Select **Build your own template in the editor**.
64+
6. Select **Load file**, and then follow the instructions to load the **template.json** file that you downloaded in the last section.
65+
7. Select **Save** to save the template.
66+
8. On the **Custom deployment** page, follow these steps:
67+
1. Select an Azure **subscription**.
68+
1. Select an existing **resource group** in the target region or create one.
69+
1. For **Region**, select the target region. If you selected an existing resource group, this setting is read-only.
70+
1. For the **topic name**, enter a new name for the topic.
71+
1. Select **Review + create** at the bottom of the page.
72+
73+
:::image type="content" source="./media/move-custom-topics-across-regions/deploy-template.png" alt-text="Custom deployment":::
74+
1. On the **Review + create** page, review settings, and select **Create**.
75+
76+
## Verify
77+
78+
1. After the deployment succeeds, select **Go to resource**.
79+
80+
:::image type="content" source="./media/move-custom-topics-across-regions/navigate-custom-topic.png" alt-text="Go to resource":::
81+
1. Confirm that you see the **Event Grid Topic** page for the custom topic.
82+
1. Follow steps in the [Route custom events to a web endpoint](custom-event-quickstart-portal.md#send-an-event-to-your-topic) to send events to the topic. Verify that the webhook event handler is invoked.
83+
84+
## Discard or clean up
85+
To complete the move, delete the custom topic in the source region.
86+
87+
If you want to start over, delete the topic in the target region, and repeat steps in the [Prepare](#prepare) and [Recreate](#recreate) sections of this article.
88+
89+
To delete a custom topic by using the Azure portal:
90+
91+
1. In the search window at the top of Azure portal, type **Event Grid Topics**, and select **Event Grid Topics** from search results.
92+
2. Select the topic to delete, and select **Delete** from the toolbar.
93+
3. On the confirmation page, enter the name of the resource group, and select **Delete**.
94+
95+
To delete the resource group that contains the custom topic by using the Azure portal:
96+
97+
1. In the search window at the top of Azure portal, type **Resource groups**, and select **Resource groups** from search results.
98+
2. Select the resource group to delete, and select **Delete** from the toolbar.
99+
3. On the confirmation page, enter the name of the resource group, and select **Delete**.
100+
101+
## Next steps
102+
You learned how to move an Event Grid custom topic from one region to another region. See the following articles for moving system topics, domains, and partner namespaces across regions.
103+
104+
- [Move system topics across regions](move-system-topics-across-regions.md).
105+
- [Move domains across regions](move-domains-across-regions.md).
106+
107+
To learn more about moving resources between regions and disaster recovery in Azure, see the following article: [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).
Lines changed: 106 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
1+
---
2+
title: Relocate an Azure Event Grid domains to another region
3+
description: This article shows you how to move Azure Event Grid domains from one region to another region.
4+
author: anaharris-ms
5+
ms.author: anaharris
6+
ms.date: 05/14/2024
7+
ms.service: application-gateway
8+
ms.topic: concept
9+
ms.custom:
10+
- subject-relocation
11+
#Customer intent: As an Azure service administrator, I want to be able to move Event Grid domains from one region to another region to have it closer to customers, to meet internal policy and governance requirements, or in response to capacity planning requirements.
12+
---
13+
14+
# Relocate Azure Event Grid domains to another region
15+
16+
This article covers the recommended approach, guidelines, and practices to relocate Event Grid domain to another region.
17+
18+
19+
Here are the high-level steps covered in this article:
20+
21+
- **Export the domain** resource to an Azure Resource Manager template.
22+
23+
> [!IMPORTANT]
24+
> The domain resource and topics in the domain are exported to the template. Subscriptions to domain topics aren't exported.
25+
- **Use the template to deploy the domain** to the target region.
26+
- **Create subscriptions for domain topics manually** in the target region. When you exported the domain to a template in the current region, subscriptions for domain topics aren't exported. So, create them after the domain and domain topics are created in the target region.
27+
- **Verify the deployment**. Send an event to a domain topic in the domain and verify the event handler associated with the subscription is invoked.
28+
- To **complete the move**, delete domain from the source region.
29+
30+
## Prerequisites
31+
32+
- Ensure that the Event Grid service is available in the target region. See [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=event-grid&regions=all).
33+
34+
## Prepare
35+
To get started, export a Resource Manager template for the domain.
36+
37+
1. Sign in to the [Azure portal](https://portal.azure.com).
38+
2. In the search bar, type **Event Grid Domains**, and select **Event Grid Domains** from the results list.
39+
40+
:::image type="content" source="./media/move-domains-across-regions/search-domains.png" alt-text="Search for and select Event Grid domains":::
41+
3. Select the **domain** that you want to export to a Resource Manager template.
42+
43+
:::image type="content" source="./media/move-domains-across-regions/select-domain.png" alt-text="Select the domain":::
44+
4. On the **Event Grid Domain** page, select **Export Template** under **Settings** on the left menu, and then select **Download** on the toolbar.
45+
46+
:::image type="content" source="./media/move-domains-across-regions/export-template-download.png" alt-text="Export template -> Download" lightbox="./media/move-domains-across-regions/export-template-download.png":::
47+
48+
> [!IMPORTANT]
49+
> Domain and domain topics are exported. Subscriptions for domain topics aren't exported. So, you need to create subscriptions for domain topics after you move domain topics.
50+
5. Locate the **.zip** file that you downloaded from the portal, and unzip that file to a folder of your choice. This zip file contains template and parameters JSON files.
51+
1. Open the **template.json** in an editor of your choice.
52+
8. Update `location` for the **domain** resource to the target region or location. To obtain location codes, see [Azure locations](https://azure.microsoft.com/global-infrastructure/locations/). The code for a region is the region name with no spaces, for example, `West US` is equal to `westus`.
53+
54+
```json
55+
"type": "Microsoft.EventGrid/domains",
56+
"apiVersion": "2020-06-01",
57+
"name": "[parameters('domains_spegriddomain_name')]",
58+
"location": "westus",
59+
```
60+
1. **Save** the template.
61+
62+
## Redeploy
63+
Deploy the template to create the domain and domain topics in the target region.
64+
65+
1. In the Azure portal, select **Create a resource**.
66+
2. In **Search the Marketplace**, type **template deployment**, and then press **ENTER**.
67+
3. Select **Template deployment**.
68+
4. Select **Create**.
69+
5. Select **Build your own template in the editor**.
70+
6. Select **Load file**, and then follow the instructions to load the **template.json** file that you downloaded in the last section.
71+
7. Select **Save** to save the template.
72+
8. On the **Custom deployment** page, follow these steps:
73+
1. Select an Azure **subscription**.
74+
1. Select an existing **resource group** in the target region or create one.
75+
1. For **Region**, select the target region. If you selected an existing resource group, this setting is read-only.
76+
1. For the **domain name**, enter a new name for the domain.
77+
1. Select **Review + create**.
78+
79+
:::image type="content" source="./media/move-domains-across-regions/deploy-template.png" alt-text="Deploy template":::
80+
1. After the validation of the template succeeds, select **Create** at the bottom of the page to deploy the resource.
81+
1. After the deployment succeeds, select **Go to resource group** to navigate to the resource group page. Confirm that there's a domain in the resource group. Select the domain. Confirm that there are domain topics in the domain.
82+
83+
84+
85+
## Discard or clean up
86+
To complete the move, delete the domain in the source region.
87+
88+
If you want to start over, delete the domain in the target region, and repeat steps in the [Prepare](#prepare) and [Recreate](#recreate) sections of this article.
89+
90+
To delete a domain by using the Azure portal:
91+
92+
1. In the search window at the top of Azure portal, type **Event Grid Domains**, and select **Event Grid Domains** from search results.
93+
2. Select the domain to delete, and select **Delete** from the toolbar.
94+
3. On the confirmation page, enter the name of the resource group, and select **Delete**.
95+
96+
To delete the resource group that contains the domain by using the Azure portal:
97+
98+
1. In the search window at the top of Azure portal, type **Resource groups**, and select **Resource groups** from search results.
99+
2. Select the resource group to delete, and select **Delete** from the toolbar.
100+
3. On the confirmation page, enter the name of the resource group, and select **Delete**.
101+
102+
## Related content
103+
104+
- [Relocate system topics across regions](move-system-topics-across-regions.md).
105+
- [Relocate custom topics across regions](move-custom-topics-across-regions.md).
106+

0 commit comments

Comments
 (0)