Update public-ip-basic-upgrade-guidance.md

Author: cburuzie

articles/virtual-network/ip-services/public-ip-basic-upgrade-guidance.md

@@ -47,6 +47,7 @@ We recommend the following approach to upgrade to Standard SKU public IP address
   | VPN Gateway (using Basic IPs) | A migration path will be provided in the future. When this migration path is available, we update this decision path with migration information and send out a service health alert. For more information, see [Migrating a basic SKU FAQ](../../vpn-gateway/vpn-gateway-vpn-faq.md#migrating-a-basic-sku-public-ip-address-to-standard-sku). |
   |  ExpressRoute Gateway (using Basic IPs) | ExpressRoute Gateway migration is required. Follow the [ExpressRoute Gateway migration guidance](../../expressroute/gateway-migration.md)   |
   | Application Gateway (v1 SKU) | New AppGW SKU required. Use this [migration script to migrate from v1 to v2](../../application-gateway/migrate-v1-v2.md).  |
+  | Azure Databricks (using Basic IPs) | For ephemeral workloads, Standard SKU public IP addresses will be deployed as virtual machines (VMs) cycle out through regular usage attrition with new VMs. For long running workloads, it is recommended to [restart compute](..//databricks/compute/clusters-manage.md#restart) which will replace the exisiting Basic IP with Standard IP.  |
 
 > [!NOTE]
 > If you have a virtual machine scale set (uniform model) with public IP configurations per instance, note these aren't Public IP resources and as such can't be upgraded; a new public IP address is required. You can use the SKU property to specify that Standard IP configurations are required for each VMSS instance as shown [here](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine).