Unanswered

Critical Issue with Copilot Studio: iframe Removed, Bot Cannot Be Published Without Authentication

(2) Share

Report

Posted on by AmelieS

Hello,

We have developed a virtual assistant using Copilot Studio (formerly Power Virtual Agents), which suddenly stopped working on July 9th. It seems likely that a Microsoft update is involved.

Here are the details of our situation—I hope you can help!

🔧 Symptoms
The bot developed with Copilot Studio has not been functioning properly since July 9, 2025.
Instead of the welcome message, an error message appears: "javascripterror".
The iframe embedding option (classic Web channel) has disappeared.
The new "Web App" channel provides a link that cannot be directly embedded on a public website.

🔐 Workaround Attempt
We tried configuring the bot with "No authentication" to make it publicly accessible.
However, publishing fails because all the bot’s topics use Power Automate flows with user connections (C2).
These connections require Azure AD authentication, which is incompatible with a public bot without authentication.

Do you know why we are facing this issue?
Is there a way to bypass these new rules and get our bot back online?

Thank you in advance for any help you can provide.

Amélie

Categories:

Bot administration

I have the same question (3)

All responses (4)

Answers (0)

Sort by

Michael E. Gernaey 53,969 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @AmelieS

Just in case you didn't see this,

Integrate web or native apps with Microsoft 365 Agents SDK - Microsoft Copilot Studio | Microsoft Learn

In this case, I would suspect that you should be using a Service Principal so you can still access the back end stuff, while not requiring context (authentication) from your users. At least this is how I have and would set it up.

I believe that is what you need to do.

That document explains how to do that in that scenario.

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No
AmelieS 49 on at

Like (0)

Report
Copy link

Link copied!

Hello!

Thank you very much @Michael E. Gernaey for your feedback and these details.
I’ll try to follow the recommendation to use a Service Principal. I’ll keep you updated on the outcome

Thanks again

Amélie

Was this reply helpful? Yes No
AmelieS 49 on at

Like (0)

Report
Copy link

Link copied!
Hi @Michael E. Gernaey

Thanks a lot for your suggestion and for sharing the documentation link.

I initially followed the approach you recommended — setting up a Service Principal via Azure App Registration, granting Microsoft Graph permissions, and creating an application user in Power Platform. The goal was to allow my Copilot Studio bot to execute Power Automate flows without requiring user authentication.

However, after extensive testing, I’ve found that this setup does not currently work for scenarios involving Excel, Outlook, and SharePoint connectors in Power Automate. Specifically:

The Excel Online (Business) connector in Power Automate does not support Service Principal authentication. It requires a user-based connection, and there’s no option to use an app identity.

Even though Microsoft Graph technically supports Service Principal access to Excel files, Power Automate does not expose this capability through its standard connectors.

As a result, publishing the bot without user authentication fails if the flows rely on these connectors, regardless of the Service Principal setup.

So unfortunately, while the theory is sound and the documentation suggests it should work, in practice, Power Automate connectors are not yet compatible with Service Principal authentication for these services.

Given this limitation, I’m now considering using a dedicated Azure AD user account instead of my personal account, to isolate the bot’s connections and maintain compatibility with Power Automate.

Do you know if this approach — using a dedicated user account — would allow me to publish the bot publicly without requiring authentication from end users, even if the flows use user-based connections? Or do you have any other suggestions ?

Thanks again for your help and insights!

Best regards,
Amélie

Was this reply helpful? Yes No
Charbel MATTAR 4 on at

Like (0)

Report
Copy link

Link copied!

Hello @AmelieS

Have you found a solution to this problem? I need to perform the same implementation, but I am stuck at the same stage.

Best regards,
Charbel MATTAR

Was this reply helpful? Yes No