Not able to publish bot after upgrading composer to 1.3.0
See original GitHub issueNot able to publish bot to Azure using Bot Framework Composer (v1.3.0).
Describe the bug
When I click [Publish selected bots] it asks to login to Microsoft account. When I enter my Azure credential it gives the below error. “This username may be incorrect. Make sure you typed it correctly. Otherwise, contact your admin.”
However, I am able to login to Azure portal or Microsoft account using the same credential.
Version
v1.3.0
OS
Windows 10 Pro
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Publish a bot to Azure from Composer - Microsoft Learn
In the Publish your bots pane, select the bot to publish, then select a publish profile from the Publish target drop-down list.
Read more >Download Composer Latest: v2.5.1
2.5.1 2022‑12‑22 changelog
2.5.0 2022‑12‑20 changelog
2.4.4 2022‑10‑27 changelog
2.4.3 2022‑10‑14 changelog
Read more >Drupal 8 Composer Best Practices - Lullabot
Whether you are new to Composer or a seasoned pro, check out these best practices for managing your Drupal 8 project.
Read more >Change Log for Plesk Obsidian
Updating Plesk on Cloud images from Ubuntu 20.04 to Ubuntu 22.04 LTS. The update will take place gradually after release 18.0.48. It is...
Read more >unable to deploy web forms built using composer in BPM 12.2 ...
I am not able to deploy web forms created in composer on BPM 2.2.1.3.0. I can build a process and deploy the process...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @NanheGupta ,
If you are trying to login with a personal Microsoft account (non-work / school) then authentication will not work.
This is a configuration issue on our end and we are currently working to fix it, but we have to wait on an external team to make a change.
This issue might be resolved once #5393 is fixed. I will update this issue when auth for MSA accounts is enabled.