Unsupported connectors when embedding Canvas App in Power Pages – any guidance docs?

(1) Share

Report

Posted on by MA-27110721-0

Hi all,

I’m embedding a Canvas App inside Power Pages using an iframe. I’ve heard that some connectors like Office365Users, Office365Outlook, Teams, OneDrive for Business, Power BI, etc., do not work or behave inconsistently, especially for portal/external users.

I understand Dataverse is the recommended data source for Power Pages, but I’m unable to find any documentation that clearly explains:

Which connectors are unsupported or limited in this scenario

Whether this behavior is by design

Is there any Microsoft doc or official guidance confirming these limitations and the recommended approach (e.g., Dataverse + Power Automate)?

Any references would be appreciated. Thanks

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Suriyanarayanan V 141 on at

Like (0)

Report
Copy link

Link copied!
You’re right to question this — Canvas Apps embedded in Power Pages via iframe do not support many connectors, especially Microsoft 365 connectors like:

Office365Users

Office365Outlook

Teams

OneDrive for Business

SharePoint (delegated user context)

Power BI (embedded)

This is by design, and Microsoft has documented the limitation — just not in a single “master list,” which is why it’s confusing.

Why these connectors don’t work in Power Pages

When you embed a Canvas App inside Power Pages:

1. The Canvas App runs under the portal user’s identity

External users (B2B, local accounts, External ID, etc.) do not have Microsoft 365 identities inside your tenant.

So Microsoft 365 connectors cannot authenticate them.

2. Power Pages does not pass through Microsoft 365 delegated permissions

Even if the iframe loads, the connectors require:

A Microsoft 365 license

A Microsoft Entra ID account in the same tenant

Delegated permissions

Portal users do not meet these requirements.

3. Microsoft explicitly states that embedded Canvas Apps are only supported for users in the same tenant

From Microsoft Learn:

“Only Power Apps users in the same tenant can access the embedded app.”

This means external/portal users cannot use connectors that rely on tenant identity.

https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/embed-apps-dev

Which connectors are unsupported or unreliable in Power Pages?

Microsoft 365 connectors (unsupported for external users)

Office365Users

Office365Outlook

Office365Groups

Teams

OneDrive for Business

SharePoint (delegated user context)

Excel Online (Business)

Planner

To Do

Power BI (requires M365 identity)

Connectors requiring delegated permissions

Anything that requires the user’s Microsoft 365 token will fail.

Connectors requiring interactive login

Portal users cannot complete the OAuth popup inside an iframe.

Which connectors do work reliably?

Dataverse (recommended)

Custom connectors using application permissions

HTTP + Azure AD app registration

Power Automate flows triggered from Canvas App

Anonymous or API-key based connectors

These work because they do not depend on the portal user having a Microsoft 365 identity.

Is this behaviour documented by Microsoft?

Yes — but spread across multiple docs:

1. Embedding Canvas Apps

Microsoft states that embedded apps only work for users in the same tenant.

This implicitly excludes external/portal users from using M365 connectors.

https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/embed-apps-dev

2. Connector authentication model

Microsoft 365 connectors require:

A Microsoft 365 license

A Microsoft Entra ID account in the same tenant

Delegated permissions

Portal users do not satisfy these requirements.

3. Power Pages guidance

Microsoft recommends:

Dataverse as the data layer

Power Automate for external operations

Avoiding direct Microsoft 365 connectors for portal scenarios

Recommended architecture (Microsoft‑aligned)

If you need to use Microsoft 365 services from Power Pages:

Use this pattern:

Canvas App → calls Power Automate

Power Automate → uses Microsoft 365 connectors

Flow returns data to the Canvas App

This works because:

The flow runs under a service account

The portal user does not need Microsoft 365 permissions

Authentication is handled server‑side

This is the officially recommended approach for Power Pages + Canvas Apps.

Was this reply helpful? Yes No
Suggested answer

oliver.rodrigues 9,396 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
wow, looks like @Suriyanarayanan V put "a lot of effort into" helping you out here

my first question to you is why do you want to embed a Canvas App into power pages?

A few things here:

Power Pages is meant for an external audience - Canvas App is meant for internal audience (Entra ID)

Power Pages relies on Dataverse data (you can also use external data, but works best with dataverse data)

Where is your Canvas App data coming from?

Who are your final users (Portal users)?

Was this reply helpful? Yes No
MA-27110721-0 8 on at

Like (0)

Report
Copy link

Link copied!
@oliver.rodrigues,
first of all, thank you for taking the time to respond.

The primary reason for embedding a Canvas App into Power Pages is URL customization. By default, the Canvas App URL looks like:

https://apps.powerapps.com/play/e/default-APPID/ENVID,

and my manager wants the URL to include our company name, which isn’t possible with native Power Apps URLs.

As a workaround, we are considering Power Pages, where we can host the app under a branded URL and embed the Canvas App using an iframe.

Before moving ahead with this approach, I want to clearly understand the limitations and supported scenarios—especially around connectors, authentication, and data sources—so we can make an informed architectural decision.

To answer your questions:

Data source: Sharepoint(All the Data coming from Power Automate)

End users: Internal users (Entra ID authenticated)

My goal here is to confirm whether embedding a Canvas App in Power Pages for this purpose is supported by design and what constraints we should expect.

Thanks again for your guidance.

Was this reply helpful? Yes No
Suggested answer

oliver.rodrigues 9,396 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
My good friend Arpit has done a very detailed end-2-end video on embedding a Canvas App on Power Pages: Integrate PowerApps with Power Pages | Embed Canvas App in Power Pages Site

this might be a good start if that's where you want to go

For internal apps, I usually don't have an issue with my customers on the URL format, strange that your manager is pushing for it. A few other options/ideas:

Use a redirect service

via DNS

via an Azure resource (web app / api management / or something)

even via Power Pages would be possible

this would simply redirect the user to the Canvas App

Embedding on Power Pages would work, I just wouldn't use it for the purpose of hiding the URL

Was this reply helpful? Yes No

Ronak

2 on at

Like (0)

Report

Copy link

Link copied!

1. Unsupported/Limited Connectors

Essentially, any connector that uses "User-Based" (Delegated) authentication will fail for external portal users.

Category	Specific Connectors	Why they fail
Productivity	Office 365 Users, Outlook, OneDrive	Requires a M365 license and a mailbox in the host tenant.
Collaboration	Microsoft Teams, Planner, SharePoint*	SharePoint can work via B2B Guest accounts, but it's notoriously flaky in an iframe.
Analytics	Power BI (Direct Connector)	Power Pages users don't have Power BI Pro/Premium per-user licenses.
Management	Entra ID (Azure AD), Power Automate Management	These strictly require internal admin/user permissions.

2. Is this behavior "By Design"?

Yes. Microsoft explicitly states in their that:

"Only Power Apps users in the same tenant can access the embedded app."

While you can share a Canvas App with Guest Users (B2B), the overhead of managing those guests just to get an iframe to work in Power Pages is usually considered "anti-pattern" for a scalable portal.

3. The Recommended Architecture (Dataverse + Power Automate)

The industry standard for bypassing these identity limits is to move the "Identity" from the Client (Canvas App) to the Server (Power Automate).

The "Proxy" Pattern:

Dataverse as the Buffer: The Canvas App writes a "request" record to a Dataverse table (which it can do, since Power Pages users have Dataverse permissions via Table Permissions).
Triggered Flow: A Power Automate flow triggers on that Dataverse record.
Service Account Context: The Flow runs under a Service Account (an internal user with an M365 license).
Action: The Flow sends the email via Outlook, creates the Teams message, or fetches the OneDrive file.
Response: The Flow updates the Dataverse record or sends a response back to the Canvas App using the PowerApp.RespondToPowerApp() action.

Official Documentation Links

Authentication Limits: https://www.google.com/search?q=https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/share-app-guests%23considerations-and-limitations-for-guest-access
Power Pages Architecture: https://www.google.com/search?q=https://learn.microsoft.com/en-us/power-pages/security/white-paper(Refer to the "External Identities" section).
Embedded Guidelines: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/embedded-canvas-app-guidelines (Note: These focus on Model-Driven, but the identity logic applies).

Was this reply helpful? Yes No

Join the conversation

Community site session details

Unsupported connectors when embedding Canvas App in Power Pages – any guidance docs?

Why these connectors don’t work in Power Pages

1. The Canvas App runs under the portal user’s identity

2. Power Pages does not pass through Microsoft 365 delegated permissions

3. Microsoft explicitly states that embedded Canvas Apps are only supported for users in the same tenant

Which connectors are unsupported or unreliable in Power Pages?

Microsoft 365 connectors (unsupported for external users)

Connectors requiring delegated permissions

Connectors requiring interactive login

Which connectors do work reliably?

Is this behaviour documented by Microsoft?

1. Embedding Canvas Apps

2. Connector authentication model

3. Power Pages guidance

Recommended architecture (Microsoft‑aligned)