Cross-Tenant Agent Sharing Failure with Dynamic OAuth

[talhelfgott666]

Describe the bug

Hey team! 👋

First off, thanks for all the work on the Agent Toolkit — it's been great to work with. I ran into something I can't quite figure out and would love a hand.

I've built an agent using the Agent Toolkit, with Dynamic OAuth for our MCP server.

ai-plugin.json

    "runtimes": [
        {
            "type": "RemoteMCPServer",
            "spec": {
                "url": "..",
                "mcp_tool_description": {
                    "file": "mcp-tools.json"
                }
            },
            "run_for_functions": [
                "execute_endpoint",
                "execute_write_endpoint",
                "fetch",
                "find_endpoints",
                "get_endpoint_detail",
                "get_endpoints",
                "search"
            ],
            "auth": {
                "type": "OAuthPluginVault",
                "reference_id": "${{MCP_DA_AUTH_ID_AIGATEWAYT}}"
            }
        }
    ]
}

declarativeAgent.json

{
    "$schema": "https://developer.microsoft.com/json-schemas/copilot/declarative-agent/v1.7/schema.json",
    "version": "v1.7",
...
    "actions": [
        {
            "id": "action_1",
            "file": "ai-plugin.json"
        }
    ]
}

What happens

1. In my own org — everything works great ✅

When I install the agent and ask a question, I get the sign-in prompt as expected:

I sign in, and I get my answer. 🎉

2. In a second account — no sign-in prompt at all ❌

I exported the agent (zipped it) and uploaded it to another account we have. When I ask a question there, no sign-in button ever shows up:

Extra detail (-developer on)

I turned on developer mode to compare the two.

Main account:

Shared account:

My guess

It looks like sharing the agent doesn't also share the plugin / MCP / connector behind it — so the second account has no auth configuration to trigger a sign-in against. Happy to be wrong here though! 🙂

What we're trying to do

We'd like to publish this agent (and its MCP server) so all of our users can use it. Our setup only supports dynamic OAuth — static isn't an option for us.

Is this expected behavior, and is there a supported path for distributing an agent with a dynamic-OAuth MCP server across accounts? Any pointers would be hugely appreciated. Thanks so much! 🙏

[m365-agent-toolkit-assistant]

👋 Hi @talhelfgott666,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Classification: By design — the sign-in prompt depends on an auth config in the Microsoft Enterprise token store, and cross-tenant use is blocked if that config is restricted to one org/app.

• Docs say plugin auth uses an auth config referenced by auth.reference_id; it isn’t just the ZIP contents.
• Official guidance: in Teams Developer Portal, Restrict usage by org must be Any Microsoft 365 organization for cross-tenant use; My organization only is for single-tenant dev/test.
• Docs also note Restrict usage by app and mismatched reference_id/base URL can prevent sign-in or token exchange.
• I found no similar issues in the searched repo.

What to do now:

1. In Teams Developer Portal, open the OAuth client registration behind MCP_DA_AUTH_ID_AIGATEWAYT.
2. Set Restrict usage by org = Any Microsoft 365 organization.
3. Verify Restrict usage by app and the plugin reference_id/base URL match.
4. Reprovision/republish, then retest in the second tenant.

Useful links:

• No similar issues found in the searched repos.
• https://learn.microsoft.com/microsoft-365/copilot/extensibility/plugin-authentication-oauth
• https://learn.microsoft.com/microsoft-365/copilot/extensibility/plugin-authentication-troubleshooting
• https://learn.microsoft.com/microsoft-365/copilot/extensibility/plugin-authentication

If you want, I can help verify the exact auth-config settings to use.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!