URGENT ACTION: Stop using az416426.vo.msecnd.net

Nobody has claimed this yet.

# ACTION REQUIRED: Stop using az416426.vo.msecnd.net

To avoid any global OUTAGE you MUST change ALL of your CDN usage from “https://az416426.vo.msecnd.net/scripts/..” to our primary CDN endpoint https://js.monitor.azure.com/scripts/...

- CDN Endpoint Change: All references to “az416426.vo.msecnd.net” must be updated to “js.monitor.azure.com” to prevent service disruptions due to a possible issue related to our current CDN configuration, this change MUST be done by Jan 15th, 2025.
- We have identified some migration challenges with the legacy domain “az416426.vo.msecnd.net” which may lead to a temporary or permanent outages.
- Action Required: Organizations must update their references and deploy changes to production before the service is disabled, and ensure that their sites can handle the absence of the Application Insights JS SDK from the CDN.

Right now we are expecting that there WILL be either a **temporary or permanent outage** of this domain based on the currently known details around the legacy domain.

## What do you need to do?

- Change ALL references of “az416426.vo.msecnd.net” to “js.monitor.azure.com”
- Deploy the change to production before this external upcoming change occurs (we don’t control the timeframe)
- Ensure that your site can handle when Application Insights JS Sdk cannot be loaded from the CDN without breaking your functionality

## Details

Both the `az416426.vo.msecnd.net` and `js.monitor.azure.com` source their files from the same location as such all files and content is identical regardless of which domain endpoint you use.

## Workarounds

- Stop using “az416426.vo.msecnd.net” and change to “js.monitor.azure.com”
- There is currently NO other workaround

We are currently investigating the available options on how we can avoid / migrate / mitigate this situation, but at this point it is **HIGHLY** likely that there will be either a temporary or permanent outage of this domain. As we currently have no known way to “migrate” this domain to a different CDN.

Any updates will be added to this issue.

No files or tests are named. Start with a repository-wide search for az416426.vo.msecnd.net, update each reference to js.monitor.azure.com, then run the project’s existing checks to confirm the SDK still builds and the legacy hostname no longer appears.

Written by the indexing model from the issue text.