Skip to content

Commit e28e99a

Browse files
authored
Update GEI documentation to use correct virtual network firewall rules when using Azure Blob Storage (#56933)
1 parent d1ec88b commit e28e99a

File tree

2 files changed

+2
-6
lines changed

2 files changed

+2
-6
lines changed

content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/managing-access-for-a-migration-from-azure-devops.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -90,10 +90,6 @@ To grant the migrator role using the CLI, you must have installed the {% data va
9090

9191
{% data reusables.enterprise-migration-tool.identifying-githubs-ip-ranges %}
9292

93-
### Virtual network firewall rules for Azure Blob Storage for {% data variables.product.prodname_dotcom_the_website %}
94-
95-
{% data reusables.enterprise-migration-tool.identify-gei-vnet-firewall-rules %}
96-
9793
### IP ranges for {% data variables.enterprise.data_residency_site %}
9894

9995
{% data reusables.enterprise-migration-tool.ip-ranges-ghecom %}
Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
Customers with Azure Blob Storage configured for storing repository data for migrations must add virtual network firewall rules to their storage accounts to allow GEI to access the repository data. This requires the use of the Azure CLI or PowerShell, as adding these virtual network firewall rules on the Azure Portal is currently unsupported. The following virtual network subnet IDs must be added to the virtual network firewall rules for your storage account:
22

3-
* `/subscriptions/495e10ff-6097-4190-a1de-b031fcb96f66/resourceGroups/ghr-network-service-4c5846fa-dc07-4153-8d08-a16a9b437a5a-3-eastus2/providers/Microsoft.Network/virtualNetworks/4c5846fa-dc07-4153-8d08-a16a9b437a5a-3/subnets/4c5846fa-dc07-4153-8d08-a16a9b437a5a-3`
4-
* `/subscriptions/d3bde7c9-46be-429b-81a8-258387be6dde/resourceGroups/ghr-network-service-4c5846fa-dc07-4153-8d08-a16a9b437a5a-3-westus3/providers/Microsoft.Network/virtualNetworks/4c5846fa-dc07-4153-8d08-a16a9b437a5a-3/subnets/4c5846fa-dc07-4153-8d08-a16a9b437a5a-3`
3+
* `/subscriptions/cdf1c65c-e6f4-43b3-945f-c5280f104f9c/resourceGroups/ghr-network-service-1a72ec6f-45b6-44be-a4bd-f0fe50079c9f-5-westus2/providers/Microsoft.Network/virtualNetworks/1a72ec6f-45b6-44be-a4bd-f0fe50079c9f-5/subnets/1a72ec6f-45b6-44be-a4bd-f0fe50079c9f-5`
4+
* `/subscriptions/173ad082-b20d-4d44-8257-7fbf34959bed/resourceGroups/ghr-network-service-1a72ec6f-45b6-44be-a4bd-f0fe50079c9f-5-westus3/providers/Microsoft.Network/virtualNetworks/1a72ec6f-45b6-44be-a4bd-f0fe50079c9f-5/subnets/1a72ec6f-45b6-44be-a4bd-f0fe50079c9f-5`
55

66
To add the virtual network firewall rules to your Azure Storage account, you can follow step 5 in the documentation for [creating a virtual network rule for Azure Storage](https://learn.microsoft.com/azure/storage/common/storage-network-security-virtual-networks?tabs=azure-cli) using the network subnet IDs provided above. Be sure to provide the `--subscription` argument with the subscription ID tied to the storage account.

0 commit comments

Comments
 (0)