Service Azure qui fournit un environnement intégré pour le développement de bot.
Bot Framework Developer Portal shows blank page — /Client/Generated/v4/all.js returns HTTP 404
Hello Microsoft Bot Framework Support and Community,
I am experiencing an issue with the legacy Microsoft Bot Framework Developer Portal.
Problem
When I open https://dev.botframework.com/bots, the page remains completely blank, preventing me from accessing my existing bot registration and updating its messaging endpoint.
Technical investigation
I reproduced the issue in Chrome on Android and independently checked the HTTP responses from my development terminal:
- "GET https://dev.botframework.com/bots" → HTTP 200
- "GET https://dev.botframework.com/Client/Generated/v4/all.js" → HTTP 404
- Other JavaScript dependencies, including jQuery and React, return HTTP 200.
The portal HTML references "/Client/Generated/v4/all.js", but that resource is unavailable. This appears to prevent the portal interface from loading.
Impact
My existing bot is connected to Microsoft Teams and Direct Line. I need to update its Messaging Endpoint to point to a new HTTPS development server.
The server itself is reachable and its Bot Framework authentication has been tested. The issue is accessing the bot management interface, not deploying the server.
Azure limitation
I am located in the Democratic Republic of the Congo (DRC), where I have encountered restrictions when attempting to create an Azure subscription.
Questions
- Is the missing JavaScript bundle a known issue with the legacy Bot Framework Developer Portal?
- Can Microsoft restore access to this portal?
- Is there an officially supported alternative to update the Messaging Endpoint of an existing legacy Bot Framework registration without creating a new bot?
- If migration is required, can the existing Microsoft App ID and Teams/Direct Line channel configuration be preserved?
- What options are available if an Azure subscription cannot be created in my country?
Please provide documented instructions or direct me to the appropriate Microsoft support team.
Thank you.