Regression after PR #301 — multi‑tenant Bot Framework auth no longer works #337
Description
We are migrating an existing Bot Framework bot to the new Agents SDK. The functional migration is complete, but we’ve recently seen an authentication regression.
Previously, removing TENANT_ID allowed our bot to authenticate and send messages using the Bot Framework multi‑tenant auth path. After PR #301, this no longer works. The change appears to be due to a removal of the old 'botframework' authority_path handling that enabled this flow.
We understand multi‑tenant Bot Framework bots are deprecated, but we need to know:
What is the correct way to configure authentication in the Agents SDK to preserve this behavior?
Specifically:
- Should we set TENANT_ID = "botframework.com" to approximate the old multi‑tenant authority?
- Or would this cause incorrect token requests or other unintended issues?
Any guidance on how to configure MsalAuth / connection settings to support the legacy multi‑tenant pattern (even temporarily) would be appreciated.