I ran into this exact issue recently, and it drove me crazy for hours. Turns out, it probably isn't your permissions or licensing.
Check Tenant Isolation in the Power Platform Admin Center.
The Problem:
Even with the right credentials and security roles, cross-tenant Dataverse connections can fail with "Token not found" or "Parameter=Token not found" errors. Dynamic content won't load, and tables won't appear.
The Real Culprit:
Power Platform Tenant Isolation policies are blocking the cross-tenant connection. It's a security feature that acts like a bouncer – and your external tenant isn't on the guest list.
The Fix (5 minutes):
Navigate:
Power Platform Admin Center → Security → Identity and Access → Tenant Isolation
- Add the external tenant ID to your allow list.
- Enable either inbound or outbound access for that tenant or both as per requirement.
- Wait a few minutes for policies to propagate
- Delete your old Dataverse connection and create a fresh one
That's it. Worked immediately for me after doing this.
Pro tip: Don't disable Tenant Isolation entirely – just whitelist the specific tenants you need to work with. Keep things secure while still getting the job done.
Hope this saves you the headache it caused me! 👍
Share
Report
All responses (
Answers (
140
