Upcoming changes to IP-addresses for Azure Relay

Published Apr 22 2022 09:00 AM 707 Views

At Azure Relay 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 Relay based solutions may break if you are not following the best practices of using domain names in your firewall or network devices configurations to allow communication with this service, but are instead using these IP-addresses.

 

We recommend using the fully qualified domain names for your specific namespaces or the general “*.servicebus.windows.net” domain, instead of using hardcoded IP-addresses. These will automatically resolve to the new configurations, meaning you won’t be impacted by these changes.

 

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

 

Region Timeframe
West Central US May 2022
North Central US May 2022

 

%3CLINGO-SUB%20id%3D%22lingo-sub-3285254%22%20slang%3D%22en-US%22%3EUpcoming%20changes%20to%20IP-addresses%20for%20Azure%20Relay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3285254%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-relay%2Frelay-faq%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAzure%20Relay%3C%2FA%3E%20we%20are%20upgrading%20our%20infrastructure%20to%20the%20newest%20technologies%2C%20allowing%20us%20to%20use%20the%20latest%20features%20available.%20Due%20to%20this%20infrastructure%20change%2C%20the%20IP-addresses%20associated%20with%20our%20customers%E2%80%99%20namespaces%20are%20also%20going%20to%20change.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYour%20Relay%20based%20solutions%20may%20break%26nbsp%3Bif%20you%20are%20not%20following%20the%20best%20practices%20of%20using%20domain%20names%20in%20your%20firewall%20or%20network%20devices%20configurations%20to%20allow%20communication%20with%20this%20service%2C%20but%20are%20instead%20using%20these%20IP-addresses.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWe%20recommend%20using%20the%20%3C%2FSPAN%3E%3CA%20style%3D%22font-family%3A%20inherit%3B%20background-color%3A%20%23ffffff%3B%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmessaging-on-azure-blog%2Fazure-wcf-relay-dns-support%2Fba-p%2F370775%22%20target%3D%22_blank%22%3Efully%20qualified%20domain%20names%3C%2FA%3E%3CSPAN%3E%20for%20your%20specific%20namespaces%20or%20the%20general%20%E2%80%9C*.servicebus.windows.net%E2%80%9D%20domain%2C%20instead%20of%20using%20hardcoded%20IP-addresses.%20These%20will%20automatically%20resolve%20to%20the%20new%20configurations%2C%20meaning%20you%20won%E2%80%99t%20be%20impacted%20by%20these%20changes.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20we%20are%20moving%20forward%20with%20implementing%20these%20changes%2C%20we%20will%20be%20updating%20this%20blogpost%20with%20the%20impacted%20regions%20and%20their%20new%20IP%20ranges.%20Below%20you%20can%20find%20the%20impacted%20regions%20that%20we%20have%20currently%20planned.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CTABLE%20border%3D%221%22%20width%3D%22100%25%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2250%25%22%3E%3CSTRONG%3ERegion%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%20width%3D%2250%25%22%3E%3CSTRONG%3ETimeframe%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3EWest%20Central%20US%3C%2FTD%3E%0A%3CTD%3EMay%202022%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2250%25%22%3ENorth%20Central%20US%3C%2FTD%3E%0A%3CTD%20width%3D%2250%25%22%3EMay%202022%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-3285254%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-relay%2Frelay-faq%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3EAzure%20Relay%3C%2FA%3E%20we%20are%20upgrading%20our%20infrastructure%20to%20the%20newest%20technologies%2C%20allowing%20us%20to%20use%20the%20latest%20features%20available.%20Due%20to%20this%20infrastructure%20change%2C%20the%20IP-addresses%20associated%20with%20our%20customers%E2%80%99%20namespaces%20are%20also%20going%20to%20change.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYour%20Relay%20based%20solutions%20may%20break%26nbsp%3Bif%20you%20are%20not%20following%20the%20best%20practices%20of%20using%20domain%20names%20in%20your%20firewall%20or%20network%20devices%20configurations%20to%20allow%20communication%20with%20this%20service%2C%20but%20are%20instead%20using%20these%20IP-addresses.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3285254%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Service%20Bus%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Co-Authors
Version history
Last update:
‎Apr 14 2022 12:53 PM
Updated by: