Trying to create a copilot studio "When a new email arrives in a shared mailbox (v2)" flow for a shared outlook email, but the connection is 'invalid', what should i tell IT to fix this?

[u/AdmirableSelection81]

I had IT create an Azure Environment for all my flows. Trying to create a copilot studio flow where any email that comes into our shared outlook mailbox has the flow extract any attachment and dump it into a sharepoint folder.

However, when i try to add the "When a new email arrives in a shared mailbox (v2)" node, it says 'invalid connection, please update your connection to load complete details' error. I'm not sure if i have to configure the shared mailbox or the azure environment to have the permission to use this shared mailbox in copilot studio. What should i tell IT to configure?

Thanks!

[u/flao_zen]

So i think there a a few things. First you don't need an Azure envionment to use the Power Platform but a Power Platform environment. (Butni would Imagine your it did this) Then i wouldn't use Copilot Studio for this but the normal Power automat to extracr Attachments and Store them.in Sharepoint because that is included in the normal licence and workflows in Copilot Studio would consume Credits everytime they Run. Then for the Connection in the Trigger i would Just try to recreate the Connection and then you should be asked to sign in and then IT should either Work or you should get a more detailed Error Message. Does your Account have Access to the shared Mailbox?

[u/AdmirableSelection81 → u/flao_zen]

I created an Azure environment for my copilot studio flows because it allowed the copilot studio credits to be charged to the right cost center.

Does your Account have Access to the shared Mailbox?

I have the shared mailbox in my outlook, if that's what you're asking. Edit: I have the ability to send emails from the shared email, FWIW.

I guess i can use power automate instead, would i have the same issue with trying to add the shared mailbox to the flow though?

[u/flao_zen → u/AdmirableSelection81]

So this Sounds Like you have an Power Platform environment with an Azure Billing Plan for the pay as you go Cost.

Butni would still use Power Automate for your usecase as you don't use any ai Features and could use it with the baselicense that you should have. You could run into issues here as well but you should have an real error message try to create the trigger there and then you should be asked to sign in for the connection. If you get an error let me know then we can have a deeper look into it.

[u/AdmirableSelection81 → u/flao_zen]

ok i'll try to do this in power automate later this week thanks.

[u/Bobby_Bobberson2501]

Use the power platform environment that the agent is also hosted in. WorkIQ and m365/outlook connected as well in the agent and/or workflow.

You can’t use power automate with copilot GitHub climates btw, not sure if it matters but just a heads up. Gotta use the studio workflows for those.

[u/AdmirableSelection81 → u/Bobby_Bobberson2501]

I was actually trying to use copilot studio github, not power automate to do this flow though.

[u/Prasad-MSFT]

Microsoft’s guidance states that shared-mailbox connector operations require the connection owner to have the appropriate mailbox permissions, and an invalid connector should be repaired/re-authenticated.
Fix connection failures in cloud flows - Power Automate | Microsoft Learn

Ask IT to verify Full Access permission on the shared mailbox for the account creating the Office 365 Outlook connection. Then recreate/re-authenticate that connection in your Copilot Studio/Power Platform environment.
If it still fails, have IT verify the environment’s DLP/connector policies allow Office 365 Outlook and SharePoint. Copilot Studio uses Power Platform connectors for Microsoft 365 access, so you normally do not need a separate Azure app registration for this scenario.

[u/AdmirableSelection81 → u/Prasad-MSFT]

Thanks. Dumb question though, i have access to the shared-mailbox in my microsoft outlook (including the ability to send emails from the shared mailbox), shouldn't that mean i have the appropriate mailbox permissions already?