-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Icons are not loaded (This site can’t be reached, spoppe-b.azureedge.net) stopped working 09.01.2025 #33596
Comments
This is happening across all versions, no icons loading here either. The worst part is that all chatbots in production all around the world generated by Azure AI Studio are also affected by this, since the repo uses this library... |
What is weird is that I have a web app in a tenant that nothing happened and looking at the Network Tab it is getting the icons from https://res.cdn.office.net/ and in another tenant another web app with the same library version it's not loading the icons and it is trying to load from https://spoppe-b.azureedge.net/ |
@duarteunp, this does not resolve the issue at hand. While rebuilding a single project might be manageable, handling multiple projects this way quickly becomes complicated. The non-responsive host should take responsibility and address the problem directly. This would be the appropriate and effective solution. |
Unfortunately, it looks like this was announced, albeit somewhat obscurely. Doesn't help, but it would seem to indicate that it's not coming back. |
The actual code for copy-paste: initializeIcons(
'https://res.cdn.office.net/files/fabric-cdn-prod_20240129.001/assets/icons/',
); |
Component
Icons
Package version
7.9.5
React version
16.14.0
Environment
Current Behavior
Expected Behavior
no errors
Reproduction
just install package and use icons.
Steps to reproduce
Are you reporting an Accessibility issue?
None
Suggested severity
Urgent - No workaround and Products/sites are affected
Products/sites affected
No response
Are you willing to submit a PR to fix?
no
Validations
The text was updated successfully, but these errors were encountered: