Resolving Flow Import Error Due to SharePoint Connector Reference

Alex Wong

Hi everyone,

Sharing a quick POSSIBLE solution for an issue you might encounter when importing a Power Automate flow (ZIP package) into your environment.

🚨 Problem

When attempting to import a packaged flow, you may see an error similar to:

Import failed for one more package resources.

This typically happens because the flow is still referencing a SharePoint site URL from the source environment (e.g., a different tenant or subdomain). Some time you will get a "Save as a new flow" link where you will be taken into editing mode of flow in draft mode and able to continue. But sometime that link does not exists.

✅ Root Cause

The flow definition includes hardcoded references to a SharePoint domain such as:

xyz.sharepoint.com

If your organization uses a different SharePoint subdomain (e.g., abc.sharepoint.com), the import will fail because the connector cannot resolve or authenticate against the original URL.

🛠️ Solution

You can resolve this by updating the flow definition before importing:

Step-by-step:

1. Unzip the flow package (.zip file)
   Extract the contents to a local folder.
2. Locate definition.json
   This file contains the flow’s configuration and connector references.
3. Open the file in a text editor
   Use Notepad, Notepad++, or similar.
4. Find and replace the SharePoint domain
   • xyz.sharepoint.com
   • abc.sharepoint.com
5. Save the file
6. Repackage the zip file
   • Ensure the structure remains unchanged when zipping it back up.
7. Re-import the flow The import should now complete successfully.

💡 Tips

• Make sure all occurrences of the old domain are replaced.
• Be careful not to alter the JSON structure.
• If multiple connectors are used, double-check for additional environment-specific URLs.

Hope this helps anyone running into this issue! Let me know if you’ve found other variations or edge cases.

Ashley Moose

This is super helpful Alex, thanks for sharing! I've been able to get around this in the past by adding the Flow into a Solution and using Environment variables but the use of Solutions has also created other challenges in some situations so will definitely be giving this a try!