Customer Advisory: Upgrade Basic Public IP SKU to Standard SKU in Azure

  • Updated on Aug 7, 2025
  • Published on Jul 30, 2025
  • 2 minute(s) read
  • AA
 Prev Next

Important Notice:

Microsoft has announced the deprecation of Basic Public IP SKU addresses in Azure, with a retirement date of September 30, 2025. After this date, Basic SKU Public IPs will no longer be supported. Customers using Basic SKU public IPs should migrate to Standard SKU public IPs before the retirement date to avoid service disruptions.

Who should be impacted?

  • Only Azure cloud Workspot customers.

  • Workspot Customer using Gateways on an Azure subscription deployed with a Basic Public IP SKU.

Please note: If your Gateway was created after March 31st, 2025, it will have the Standard Public IP SKU.

Does this upgrade require Downtime?

Yes, this requires downtime, as all the gateways in a cluster are part of the same availability set. To upgrade a Basic SKU Public IP to a Standard SKU for VMs in an Availability Set, all associated VMs and Gateways must be shut down and deallocated. This is because Azure locks the IP configuration while resources are running, preventing changes to the SKU. Deallocation releases these bindings, allowing the upgrade to proceed without errors.

If you attempt to upgrade to a Standard SKU without first deallocating all Gateway VMs in the cluster, the operation will fail with an error in the Azure portal. This is because all Gateway VMs in the cluster belong to the same availability set, which requires consistent SKU configuration across all instances.

Plan before upgrade:

  • Plan a maintenance window for the downtime.

  • Identify the Gateway server of the Gateway Cluster on the Azure subscription with the Basic Public IP SKU.

    • Log in to Azure Portal

    • In the Search bar, type "Public IP addresses" and select the result.

    • Look at the SKU column. If not available, click on Manage View > Edit Columns > Add Columns > select SKU from drop-down > Save.

    • Sort or filter by this column to quickly see all Basic SKUs.

    • Gateway VM names can be found on the infrastructure page of Workspot Watch.

      Workspot Control captures the gateway's public IP during provisioning. Any IP change in Azure afterward may cause a mismatch, which will be resolved in upcoming Control releases.

    • Private and Standalone Gateways created manually in Azure using a Basic Public IP SKU will also need to be upgraded.

Here are the steps that must be followed:

  • Put all the Gateway servers of a cluster in maintenance mode from Workspot Control. This requires a few minutes of downtime.

  • Stop and Deallocate all the gateways from the Azure console.

  • Please follow the steps below for each gateway in the cluster.

    • Click on the Public IP, under networking > Network Settings

      A screenshot of a computer AI-generated content may be incorrect.

    • Change the IP address assignment to Static and save, under Settings > Configurations

      A screenshot of a computer AI-generated content may be incorrect.

    • Disassociate the IP from the resource/NIC


      Click on “Yes” to the prompt “This action will permanently dissociate the public IP address from the network interface card.”

    • Upgrade to Standard SKU

      • Go to the disassociated Public IP address, click on the Upgrade to Standard option.

Click on “I acknowledge” and yes.

Please refer to the Microsoft document: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade?tabs=azureportal, for the steps to upgrade the Basic public IP SKU to the Standard SKU using the Azure portal, PowerShell, or Azure CLI

  • Associate the Public IP address with the Gateway Network Interface.

  • Start the Gateway VM in Azure.

  • Change the mode of the gateway in the Workspot Control from maintenance to Enable.

  • Follow the same procedures for the remaining Cluster on the Workspot Control.

If you have any questions, please get in touch with Workspot Support.