You’re offline. This is a read only version of the page.
Announcements
A PowerApp, AppA, was created using lists connected from SharePoint SiteA, and the Office 365 Outlook connector was added to allow sending an email.
A copy of the App, AppB, was made using the PowerApps Save As function, and then lists from SharePoint SiteB were used to replace the SiteA lists. (Add the lists, and then use Search/Replace to update.)
AppB did NOT need the O365Outlook connector, so it was removed.
Upon release of AppB to the ClientB users, when they try to open it, they receive the following error:
If your use case requires a cross-tenant connection, contact your tenant administrator.
Details:
Connection owner tenant: a1f05287-...,
Connection sign-in tenant: 71e34cb8-...,
Connector: Office 365 Outlook.'. The correlation Id is '5e7cf981-...
In desperation to give access to a ClientB user, we granted them access to SiteA (via SharePoint security), and this error message subsided permanently, EVEN AFTER the rights to SiteA are revoked from the ClientB user. (It's like a one-time kick in the pants, and then PowerApps doesn't need it anymore. Non-persistant.)
AppB has been scoured for any references to SiteA, and keywords like "Office", "365", "Outlook", "email", etc, and nothing can be found.
Side note: During our flailing, another App, AppXray, from another Client, which is a completely different app (not a copy like AppB), was tested by the ClientB user, and it opened without any issues.
It seems as if the Office 365 Outlook connector reference is stuck in the bowels of AppB. What method could be used to purge this, short of recreating the entire App from scratch?
Share
Report
784
All responses (
Answers (
