HubNetworking: Deploy Azure Bastion into Availability Zones

[integyjc]

Describe the feature end to end, including deployment scenario details under which the feature would occur.

The current deployment of bastion doesn't configure zone redundancy. Enabling this feature for regions which support it would increase compliance with ALZ policies around zone resilience and provide a more robust deployment

Why is this feature important. Describe why this would be important for your organization and others. Would this impact similar orgs in the same way?

Availability, compliance, best practice

Please provide the correlation id associated with your error or bug.

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Can you describe any alternatives that you have taken since this feature does not exist?

No response

Feature Implementation

Check previous GitHub issues

• I have searched the issues for this item and found no duplicate

Code of Conduct

• I agree to follow this project's Code of Conduct

[oZakari]

Hey @sebassem, as availability zones support for Bastion is in public preview as of May. Is this something we want to add to the backlog to add it in the future? Right now, it is pretty limited in what regions are supported as a heads up.

[integyjc]

Hey @sebassem, as availability zones support for Bastion is in public preview as of May. Is this something we want to add to the backlog to add it in the future? Right now, it is pretty limited in what regions are supported as a heads up.

Apologies, I hadn't spotted it was in preview before logging this! - This came back off a handover with a customer and noticing resources flagged as not being zone resilient.

[oZakari]

No worries, @integyjc, it's a good call out to make sure it's on our radar.

[sebassem]

Hey @sebassem, as availability zones support for Bastion is in public preview as of May. Is this something we want to add to the backlog to add it in the future? Right now, it is pretty limited in what regions are supported as a heads up.

Yes indeed, I added it to our backlog for the Bastion refresh. Thanks @oZakari

[oZakari]

Moving this to the upstream Enterprise-Scale repository for tracking.

[Springstone]

We don't currently deploy Bastion as part of this repo's accelerator (Portal), but is on the backlog and planned to be released as part of the next refresh (Policy Refresh FY25 Q3). As part of that implementation we will leverage Availability Zones for Bastion where possible.
The other accelerators have their own backlogs tracking this request.