Skip to content

Commit a2d6011

Browse files
committed
accessing private network from deployment scripts
1 parent 0a815e9 commit a2d6011

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/azure-resource-manager/bicep/deployment-script-bicep.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-resource-manager
55
author: mumian
66
ms.service: azure-resource-manager
77
ms.topic: conceptual
8-
ms.date: 01/18/2023
8+
ms.date: 01/24/2023
99
ms.author: jgao
1010
---
1111

@@ -630,6 +630,10 @@ When you use Azure PowerShell deployment scripts, you can use the `Invoke-RestMe
630630

631631
The identity that your deployment script uses needs to be authorized to work with the Microsoft Graph API, with the appropriate permissions for the operations it performs. You must authorize the identity outside of your Bicep file, such as by pre-creating a user-assigned managed identity and assigning it an app role for Microsoft Graph. For more information, [see this quickstart example](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.resources/deployment-script-azcli-graph-azure-ad).
632632

633+
## Access private virtual network
634+
635+
The supporting resources including the container instance can't be deployed to a private virtual network. To access a private virtual network from your deployment script, you can create another virtual network with a publicly accessible virtual machine or a container instance, and create a peering from this virtual network to the private virtual network.
636+
633637
## Next steps
634638

635639
In this article, you learned how to use deployment scripts. To walk through a Learn module:

0 commit comments

Comments
 (0)