Azure Bastion Developer SKU is missing in the supported regions.

Hello Atanu Gupta

Thank you for the response,

We have checked with the internal team, and there is an outage in the Developer SKU in the Bastion. I will inform you once the issue is resolved.

Outage details:

Impact Statement: Starting at 06:10 UTC on 02 May 2025, you have been identified as a customer using Bastion Developer who may experience unavailability for the service. Bastion Developer will be unavailable until further notice.

Workaround: We recommend using the Basic or Standard SKU of Azure Bastion to ensure continued secure access to your resources. (About Azure Bastion | Microsoft Learn)

Current Status: We are actively working to resolve the issue and restore full functionality. We are working on developing a fix and continuing to monitor this situation closely. We understand the inconvenience this may have caused and sincerely apologize for any disruption to your operations. We appreciate your understanding and patience as we work to resolve this issue. The next update will be provided on 05 May 2025, or as events warrant.

We're still experiencing the same issue in the West Europe region. We only started using Azure Bastion Developer about 2 weeks ago, we still have the Bastions in Developer tier, but we cannot use them at the moment.

Are there any updates on this?

Hello Wouter Aarts

Current Status: We are actively working to resolve the issue and restore full functionality to the service. Investigating teams have identified the issue and are in the process of developing a fix. The available workaround should help most of the affected customers, as we continue to monitor this situation closely.

We understand the inconvenience this may have caused and sincerely apologize for any disruption to your operations. We appreciate your understanding and patience as we work to resolve this issue. 

The next update will be provided on 08 May 2025, or as events warrant.

Is there an estimated timeline for resolving the issue?

Where is the update page showing the status of this issue? Azure Health Status shows all Bastions green and healthy.

Hi@Atanu Gupta

There appears to be a transient issue in the Azure portal (portal.azure.com). I also tested the same in my lab, and the Developer SKU is not showing in the Central India region in the normal portal (portal.azure.com).

We will escalate this to the product team to get it fixed and notify the relevant teams once it's resolved. Alternatively, you can also submit your feedback on the MS DOC so the team can review and update it accordingly.

Alternatively, you can use the preview portal: [https://preview.portal.azure.com/], as I have already tested it , and the Developer Plan is visible in the Central India region, as shown below.

If you're facing any errors in the Portal, kindly create it using the command below

az network bastion create --name Venkatbastion-bastion --public-ip-address VNet1-ip --resource-group TestRG1 --vnet-name VNet1 --location centralindia --sku Developer

Reference: https://learn.microsoft.com/en-us/azure/bastion/create-host-cli

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

I really appreciate your feedback. It’s valuable to us. Please click Accept Answer on this post to assist other community members facing similar issues in finding the correct solution.

While the preview portal shows the Developer SKU and prompts for credentials in existing Bastion Developer instances, it's still exiting with a connection error

Hi João Amaro

Thanks for your reply.

If you're facing an issue after creating a Bastion Developer plan, please post your question with detailed information and an error screenshot. I’ll definitely try to help you with the issue. I posted answer to the question the Developer plan not being available.

Preview portal is only showing 4 locations once you select the Developer SKU. Central India not there. It seems to be a big outage going on for weeks now.

Hi Atanu Gupta,

I just tested using the CLI command and was able to create a Developer plan in the Central India region. It appears to be a transient issue in the Azure portal.

We will escalate this to the product team to get it fixed and notify the relevant teams once it's resolved

Kindly test the same on your end and confirm.

az network bastion create --name Venkatbastion-bastion --public-ip-address VNet1-ip --resource-group TestRG1 --vnet-name VNet1 --location centralindia --sku Developer

Output:

Portal result

Reference:

https://learn.microsoft.com/en-us/azure/bastion/create-host-cli

If this helps resolve your issue, please click Accept Answer on this post to assist other community members facing similar issues in finding the correct solution.

No...the preview portal is even more funny. It shows Develop SKU in Central India region.... but once you select that SKU... the central india region vanishes. There's a big outage going on in Bastion service.

Hi Atanu Gupta

There is a transient issue in the portal. Could you please try the CLI command below and confirm

az network bastion create --name Venkatbastion-bastion --public-ip-address VNet1-ip --resource-group TestRG1 --vnet-name VNet1 --location centralindia --sku Developer

We are checking with the product team to get it fixed and will share the results with the respective groups once the issue is resolved.

If this helps resolve your issue, please click Accept Answer on this post to assist other community members facing similar issues in finding the correct solution.

But why public IP and Vnet informations are required for Developer SKU? Please fix the real issue asap and why Azure Status is not showing this bastion outage?

Why it's all green.?

Hi @Atanu Gupta**

Public IP** is not required, but a virtual network (VNet) is necessary. Azure Bastion with the Developer SKU allows you to connect to your virtual machines via private IP addresses, without needing a public IP on the VMs. The VMs you connect to do not require a public IP address. Follow the MS DOC for more details

Required parameters to execute the command: follow the az network bastion create

az network bastion create --name MyBastion --resource-group MyResourceGroup --sku Developer --vnet-name MyVnet 

If this helps resolve your issue, please click Accept Answer on this post to assist other community members facing similar issues in finding the correct solution.

The command is only successful in creating the bastion resource in Developer SKU but the bastion created this way unable to login to the VM.

I would request you to first try it yourself and then provide the answer. Not like this half baked touch-and-go kind of information.

@Atanu Gupta ,

Greetings.

Your observation is correct; there is an issue with Azure Bastion Developer SKU across regions.

Azure Bastion team is currently working on a fix to address the issue and restore full functionality. And there is no ETA as of now.

I will update this thread once we have a fix.

Cheers,

Kapil.

@Atanu Gupta ,

NOTE : Only Azure Bastion Developer SKU is affected by this, not other SKUs.

The recommended work around as of now is to use Basic or Standard SKU

Hmmmmmm ... as expected from Microsoft 😊..Please update me if you find the fix this year. Thanks.

Is there any open ticket where this issue can be tracked?

Please give more Prio to fix this. Has been down way to long now and does not give us trust in the services. The fix to deploy another SKU is not a good one. It cost us money and will drain the bucks we have to play with in our VS subscriptions, and when Microsoft fixed the developer sku we will not be able to downgrade easily.
Can you give us a more detailed update @KapilAnanth-MSFT on how you are working in this case and the status?

Shoaib Chohan, Jimmy Lindö - automated email communications are sent to customers who had an existing Azure Bastion Developer.

However, if you did not have an existing one - you can consider creating a Support incident so that a Support Engineer can work with you and give you daily updates.

NOTE: Azure Bastion Developer offering is ideal for Dev/Test users who want to securely connect to their VMs, not for Production workloads.

I too shall update this thread if there are any developments.

@KapilAnanth-MSFT I am looking in my global admin accounts mailbox that also where the account that deployed Bastion Host Developer. I cannot find any communication regarding this issue, how should it be communicated? Developer SKU is used by Visual Studio subscriptions, these subscriptions are not under a support plan so that's an issue regarding creating a support ticket on the incident. I have used this Bastion host for over 6 months and it just stopped working. No health issues are related to the service in the portal.

would be nice if this could be escalated to bring some trust in the services or at least give the real status of the service in the portal so uptime reporting will be more correct of the services.

It's really sad that nowadays it takes months for Microsoft to fix any issue. It was not like this before as i am working in Azure platform for 12+ years now.

Maybe all their layoffs and attrition has started showing results. All good tech guys might have left it seems.

Jimmy Lindö - I totally understand your concern and I completely apologize for the issue.

• Currently, the recommendation from our Product Team is to use Basic or Standard SKU.
• Should there be an ETA or regional update, I shall add it to this thread.

P.S : Please find the the email communication initiated to the affected customers below

Impact Statement: Starting at 06:10 UTC on 02 May 2025, you have been identified as a customer using Bastion Developer who may experience unavailability for the service. Bastion Developer will be unavailable until further notice.

Workaround: We recommend using the Basic or Standard SKU of Azure Bastion to ensure continued secure access to your resources. (About Azure Bastion | Microsoft Learn)

Current Status: We are actively working to resolve the issue and restore full functionality. We are working on developing a fix and continuing to monitor this situation closely. We understand the inconvenience this may have caused and sincerely apologize for any disruption to your operations. We appreciate your understanding and patience as we work to resolve this issue. The next update will be provided on 05 May 2025, or as events warrant.

Hi Atanu Gupta,

thank you for reaching out with your question about the Azure Bastion Developer SKU on the Q&A portal. I really appreciate you taking the time to engage with the community and share your concerns.

I understand you’re looking for the Developer SKU in the Central India region, and I can see how this might be confusing if it’s not appearing as expected. According to the official Microsoft documentation, the Developer SKU should indeed be available in Central India, as mentioned here: Azure Bastion Quickstart for Developer SKU.

Sometimes, regional availability can vary due to updates or temporary limitations. If you’re not seeing the Developer SKU in the dropdown or options when creating a Bastion host, it might be worth double-checking the region selection or refreshing the portal. Additionally, you could try creating the Bastion host through Azure CLI or PowerShell, as the SKU might be available there even if it’s not visible in the UI.

If the issue persists, I’d recommend checking the Azure status page for any service updates or outages that might affect SKU availability in Central India. You can find that here: Azure Status.

Let me know if you’ve already tried these steps or if you’re still running into trouble.

Best regards,
Alex
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment
https://ctrlaltdel.blog/

Its a big outage going on for months now but Azure Status is showing all GREEN for bastion. That's the funny part 😊

Same issue with East US 2 (should be available according to documentation). Microsoft: any update, ETA, ticket number?

Hi G Robert , greetings.

Currently, Azure Bastion team is working on a fix and this is Severity 1.

And we do not have a public facing ETA.

The recommendation from our Product Team is to use Basic or Standard SKU. Should there be an ETA or regional update or RCA available for us to share publicly, I shall add it to this thread.

Apologies for the inconvenience caused.

Dont give advise to use Basic or Standard SKU in every comment. Who will pay for it..Microsoft? to compensate. If your developer sku has screwed up... then say it's dead for now and push your tech guys to provide a fix asap without wasting time.

USING BASIC OR STANDARD SKU IS NOT A SOLUTION

@Atanu Gupta , I understand your concern.

We agree that there is an outage happening at Azure Bastion Developer SKU, and I can assure you the Product Team is working on it.

Note that the recommendation to use Basic or Standard is not a solution, but a workaround in the meantime.

Experiencing the same issue. Where is the issue officially reported? The service status page shows no issues. How can I be notified when it's fixed?

Still having issue today, using North Central US.

Hi @Everyone ,

Greetings.

Please refer to Connect with Azure Bastion Developer,

• 
• The document will be updated once the service becomes available.

Thanks,

Kapil

Well, its now August 5th. 3 months since the OP reported the issue. Microsoft I think 3 months is enough to warrant a status update if not a complete resolution. Still experiencing the issue on my end and its holding back progress for our clients

Preston Grant,

Refer : Connect with Azure Bastion Developer

Thanks,

Kapil

It's not a workaround to suggest other paid products in place of the product that is supposed to be included with the service. For those that have been forced to used the workaround all this time, microsoft would have even less motivation to fix the developer sku. How about providing the community with a better update or a timeline to resolution?