PowerApps triggered Flow fails on updating O365 Outlook connector account

[gsivasai]

Recently a client updated their domain from @abcdef.com to @abc.com. The original owner of the Flow triggred from PowerApps with the O365 Outlook connector was on the @abcdef.com domain. I updated the connector to use the same account but on the new @abc.com domain. The Flow starting failing with the below error:

The only way I could get Flow to work was to remove and re add the Flow connection as a data source on all PowerApps triggering the Flow. On further digging, I noticed that the mapping in the connectionsMap.json for that Flow had a reference to the property "shared_office365_1" property.

Seems to be a mismatch in what Flow is expecting to see vs what the package configuration has for reference in terms of the account being used for connectors.

Should updating the connector account require app owners to refresh Flow connections in PowerApps? Or is this a discrepancy in how connection mappings are updated when flipping between connector accounts with the same O365 Id but on different domains?

This is a crtitical part of several solutions deployed on the client's tenant. It would be very helpful to get clarity on the behavior so we can proactively manage other Flows (working okay so far) but still using the old domain account @abcdef.com for connectors.

Appreciate the help on this! Thank you!

[v-bacao-msft]

Hi @gsivasai,

You could try to export the Flow and then import it as a new Flow. Once the connection is configured, the new Flow will work.

This problem happens sometimes when you introduce new connectors to a flow after you have initially saved the flow without using that connector.

Please take a try.

Best Regards,

Barry

[gsivasai]

Thanks @v-bacao-msft for the quick response!

New connectors were not added and the Flow structure has been the same. The only change that has occured is switching the old domain (@abcdef.com) account used in the O365 Outlook Flow action to an account with the new domain (@abc.com).

Also, emport/import didn't work. The failure still occurs and seems to be tied to the way connection mapping schema is generated when accounts are updated for a connector. 

To be specific, this use case is around switching between the different domains for the same O365 account.

Any thoughts?