Azure / Enterprise-Scale

The Azure Landing Zones (Enterprise-Scale) architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture
https://aka.ms/alz
MIT License
1.72k stars 972 forks source link

Feature Request: Azure Bastion in Adventure Works and Trey Research #976

Open jonathan-vella opened 2 years ago

jonathan-vella commented 2 years ago

What is the possibility of including the option to also deploy Azure Bastion in both Adventure Works and Trey Research?

jtracey93 commented 2 years ago

Hey @jonathan-vella,

Thanks for raising this.

Have you seen: https://docs.microsoft.com/en-gb/azure/cloud-adoption-framework/ready/azure-best-practices/plan-for-virtual-machine-remote-access?

Would you want to see Bastion deployed to the spokes or in a hub?

We promote a spoke model in ALZ to keep RBAC simplified etc.

Let us know 👍

ghost commented 2 years ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days.

jonathan-vella commented 2 years ago

A very common and frequent ask from both customers and partners is to have Azure Bastion deployed in Hub as part of the AZLZ accelerator deployment.

jtracey93 commented 2 years ago

Thanks @jonathan-vella with the release of the IP Connect feature this is now more applicable https://docs.microsoft.com/en-us/azure/bastion/connect-ip-address

jtracey93 commented 2 years ago

Trigger ADO Sync 1

jtracey93 commented 2 years ago

Trigger ADO Sync 2

jonathan-vella commented 2 years ago

A very common and frequent ask from both customers and partners is to have Azure Bastion deployed in Hub as part of the AZLZ accelerator deployment.

jtracey93 commented 2 years ago

Thanks @jonathan-vella. What do they do around the additional RBAC requirements as documented here: https://learn.microsoft.com/en-gb/azure/cloud-adoption-framework/ready/azure-best-practices/plan-for-virtual-machine-remote-access