Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
Our Product Team is aware of this issue. They also assured that they have a fix that is rolling out.
The approximate ETA for this is around 2-3 weeks .
For now, the work around is to deploy Bastion using the Preview Azure poral or deploy it from the VNet/VM blade in the regular Azure portal.
- Preview Azure portal link: https://preview.portal.azure.com/ Regular Azure portal link: https://portal.azure.com/
- Refer the below docs to deploy Bastion from the Vnet/VM blade using the regular Azure portal:
- Bastion with default settings - https://learn.microsoft.com/en-us/azure/bastion/quickstart-host-portal#createvmset
- Bastion with manual settings - https://learn.microsoft.com/en-us/azure/bastion/tutorial-create-host-portal#createhost
- Bastion with default settings - https://learn.microsoft.com/en-us/azure/bastion/quickstart-host-portal#createvmset
You can also use Azure Powershell or Azure CLI to workaround this
- https://learn.microsoft.com/en-us/azure/bastion/bastion-create-host-powershell
- https://learn.microsoft.com/en-us/azure/bastion/create-host-cli
Thanks for your continued contribution on Q&A and appreciate much for taking the time to share your feedback.
Thanks,
Kapil
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.