jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-06 06:02:35 -05:00
Code Issues Projects Releases Wiki Activity

Actions Azure VNET beta documentation updates (fast follow) (#40808)

Browse Source
This commit is contained in:
Joe Clark
2023-08-17 10:04:11 -07:00
committed by GitHub
parent 898eaafed3
commit 2eb93492f3
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/actions/using-github-hosted-runners/connecting-to-a-private-network.md
View File

@@ -152,7 +152,11 @@ Before configuring {% data variables.product.prodname_actions %} for VNET-inject
{% note %}
**Note:** To configure {% data variables.product.prodname_actions %} for VNET-injection, you must use an Azure account with the Subscription Contributor role and the Network Contributor role. These roles enable you to register the resource provider and delegate the subnet. For more information, see [Azure built-in roles](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles) in the Azure documentation.
**Notes:**
- To configure {% data variables.product.prodname_actions %} for VNET-injection, you must use an Azure account with the Subscription Contributor role and the Network Contributor role. These roles enable you to register the resource provider and delegate the subnet. For more information, see [Azure built-in roles](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles) in the Azure documentation.
- To correctly associate the subnets with the right user, Azure `NetworkSettings` resources must be created in the same subscriptions where virtual networks are created.
- To ensure resource availability/data residency, resources must be created in the same Azure region.
- After you configure your Azure subscription, share your Azure Subscription ID with your {% data variables.product.company_short %} contact to enroll in the beta.
{% endnote %}
@@ -333,7 +337,7 @@ To grant {% data variables.product.prodname_actions %} access, you can use {% da
1. Use the following command in the Azure CLI to create a network settings resource in Azure. For more information, see [Azure Command-Line Interface (CLI) documentation](https://learn.microsoft.com/en-us/cli/azure/) in the Azure documentation.
```shell copy
az resource create -g RESOURCE_GROUP_NAME -n RESOURCE_NAME --resource-type GitHub.Network/networkSettings --properties @networkSettingsPayload.json
az resource create -g RESOURCE_GROUP_NAME -n RESOURCE_NAME --resource-type GitHub.Network/networkSettings --properties '@networkSettingsPayload.json' --api-version 2023-03-15-beta
```
The command will return the full payload for the created resource. The following is an example of a portion of the full payload.