Skip to content

Commit 2056822

Browse files
Merge pull request #272180 from cherylmc/Bastion-write
write-permissions
2 parents 88ff78e + b24ba0d commit 2056822

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/bastion/bastion-faq.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,10 @@ No, Azure Bastion doesn't currently support Azure Private Link.
6868

6969
At this time, for most address spaces, you must add a subnet named **AzureBastionSubnet** to your virtual network before you select **Deploy Bastion**.
7070

71+
### <a name="write-permissions"></a>Are special permissions required to deploy Bastion to the AzureBastionSubnet?
72+
73+
To deploy Bastion to the AzureBastionSubnet, write permissions are required. Example: **Microsoft.Network/virtualNetworks/write**.
74+
7175
### <a name="subnet"></a>Can I have an Azure Bastion subnet of size /27 or smaller (/28, /29, etc.)?
7276

7377
For Azure Bastion resources deployed on or after November 2, 2021, the minimum AzureBastionSubnet size is /26 or larger (/25, /24, etc.). All Azure Bastion resources deployed in subnets of size /27 before this date are unaffected by this change and will continue to work. However, we highly recommend increasing the size of any existing AzureBastionSubnet to /26 in case you choose to take advantage of [host scaling](./configure-host-scaling.md) in the future.

0 commit comments

Comments
 (0)