Blog Post

Messaging on Azure Blog
2 MIN READ

Upcoming changes to IP-addresses for Azure Service Bus

EldertGrootenboer's avatar
Apr 22, 2022

At Azure Service Bus we are upgrading our infrastructure to the newest technologies, allowing us to use the latest features available. Due to this infrastructure change, the IP-addresses associated with our customers’ namespaces are also going to change.

 

Your Service Bus based solutions may break if you are not following the best practices of using service tags or domain names in your firewall or network devices configurations to allow communication with this service, but are instead using these IP-addresses.

 

If you are using Service Bus premium, we recommend using service tags, as per our recommendations described in the service documentation. Service tags will automatically be updated if anything changes in our infrastructure, meaning you won’t have to make these changes manually.

 

If you are on Service Bus standard or cannot use service tags, we recommend using the fully qualified domain names for your specific namespaces or the general “*.servicebus.windows.net” domains. These will automatically resolve to the new configurations as well, meaning you won’t be impacted by these changes either.

 

As we are moving forward with implementing these changes, we will be updating this blogpost with the impacted regions. Below you can find the impacted regions that we have currently planned.

 

Region Timeframe
West Central US June 2023
Sweden Central  June 2023
North Central US  July 2023
UK South  July - Oct 2023
France Central  Sep - Nov 2023
Canada Central Sep - Nov 2023
Australia East Oct - Dec 2023
Switzerland North Oct - Dec 2023

Norway East

Oct - Dec 2023

East Asia 

Oct - Dec 2023

South Africa North 

Dec 2023 - Feb 2024

Australia Central 2 

Dec 2023 - Feb 2024

Australia Southeast

Dec 2023 - Apr 2024

Central India

Dec 2023 - Feb 2024

France South

Dec 2023 - Feb 2024

Japan West 

Dec 2023 - Feb 2024

Norway West

Dec 2023 - Feb 2024

South Africa West 

Dec 2023 - Feb 2024

South India

Dec 2023 - Feb 2024

Sweden South

Dec 2023 - Feb 2024

Switzerland West

Dec 2023 - Feb 2024

UAE North

Dec 2023 - Feb 2024

UK West 

Dec 2023 - Feb 2024

Australia Central 

Dec 2023 - Feb 2024

Germany North

Dec 2023 - Feb 2024

Korea South

Dec 2023 - Feb 2024

UAE Central 

Dec 2023 - Feb 2024

Brazil Southeast

Jan 2024 - Feb 2024

Canada East

Jan 2024 - Feb 2024

Central US EUAP

Jan 2024 - Feb 2024

East US 2 EUAP

Jan 2024 - Feb 2024

Asia Southeast

Jan 2024 - Feb 2024

West India 

Jan 2024 - Apr 2024

North Europe

Feb 2024 - Apr 2024

Germany West Central

Feb 2024 - Mar 2024

East US

Feb 2024 - Apr 2024

East US 2

Feb 2024 - Apr 2024

UAE North

Feb 2024 - Mar 2024

West US 3

Feb 2024 - Apr 2024

West US

Feb 2024 - Apr 2024

Remaining regions

Apr 2024 - Jun 2024

 

Last updated - 02/16/2024

Updated Jun 04, 2024
Version 10.0
  • KennethStenbeck's avatar
    KennethStenbeck
    Copper Contributor

    We are using Route Table to bypass our NVA for internal resources access to standard tier Service bus (for latency reasons). So our Service bus is not included in ServiceTag, and fqdn is not supported in route tables. Pls advise.