cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Azure basic public IP SKU retirement

Matty
New Contributor III

With Azure notifying that retirement of the basic public IP SKU in 2025 I'd like to understand how compute cluster workers can be moved over from basic to standard SKU? We've used Terraform to deploy our Databricks environment but I'd like to understand if any config changes need to be made to change over the SKUs?

7 REPLIES 7

sonia598lewis
New Contributor II

@Matty wrote:

With Azure notifying that retirement of the basic public IP SKU in 2025 I'd like to understand how compute cluster workers can be moved over from basic to standard SKU? We've used Terraform to deploy our Databricks environment but I'd like to understand if any config changes need to be made to change over the SKUs?


Hello,
To move to compute cluster workers from Basic to Standard SKU in Azure, you'll need to make some configuration changes in your Terraform setup. Here's a concise guide:

  1. Identify Resources: List all resources using Basic SKU public IPs.

  2. Create New Standard SKU IPs: Use Terraform to create new Standard SKU public IPs.

  3. Update Resources: Associate the new Standard SKU IPs with your resources.

  4. Verify: Ensure all resources are correctly using the new IPs.

You can find detailed steps in the.

Best Regards,
Sonia Lewis

Matty
New Contributor III

Hi Sonia,

Do you know under which Terraform block the additional configuration needs added to?

Thanks,

Matty

krupakar
New Contributor II

When Basic public Ip SKU is getting retired, why the databricks cluster VMs are still getting provisioned with the Basic sku IPS

Matty
New Contributor III

I contacted Microsoft, they spoke with their SME of the Databricks team who have confirmed they're aware of this and will be transitioning from Basic to Standard SKU before deprecation - a update from Microsoft will be getting released regarding this.

 

From a customers perspective there's nothing we need to do.

PNC
New Contributor II

Hi Matty,

Do you know if there is a official statement from Microsoft about this? Our platform team noticed that we have significant amount of Basic SKU Public IP addresses. I investigated and noticed that every single one of those are related to Databricks. Our Databricks configuration is handled with Terraform as well and I'm trying now to figure out if I'm supposed to make changes to the configuration or if this is something that will fix itself. I looked through our Terraform code and there's no Public IP configuration so I suppose it's using default values. 

Matty
New Contributor III

Hi PNC,

They've said there will be a communication at some point before the deprecation but never actually gave a specific date of when it'll be done, it's a bit frustrating as we'll probably keep getting alerts through saying our resources as on Basic SKU and need to upgrade until they change it over...

I've went backwards and forwards with Databricks and Microsoft and scanned through the Terraform registry many times and there's no way we can change anything relating to the SKU. It looks like it's just going to be one of those scenarios where at some point when Microsoft have made their changes Databricks jobs will scale down and when the next job runs they'll suddenly be on the Standard SKU.

PNC
New Contributor II

Great, thanks for the info!

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโ€™t want to miss the chance to attend and share knowledge.

If there isnโ€™t a group near you, start one and help create a community that brings people together.

Request a New Group