Thanks for the follow-up and for clarifying your setup. You're packaging your custom connector using a Power Platform Solution and managing it via the Power Platform CLI (pac
), not paconn
, which is the older CLI tool. You're referencing the connector icon via <iconblob>
in the connector XML, and Microsoft support suggested switching to a URL. You're asking whether you should use <iconURL>
instead and where to find documentation for the connector XML schema.
Here’s what I found based on internal documentation and Microsoft’s published resources:
<iconblob>
vs <iconURL>
<iconblob>
is used when embedding the icon directly into the solution package. This typically references a local file path (e.g., icon.png
) that gets bundled during packaging.<iconURL>
is used when referencing an externally hosted image (e.g., on a CDN or SharePoint). This avoids packaging the image and can resolve broken image issues if the packaging or deployment process fails to embed the icon correctly.If you're experiencing broken image issues and Microsoft support suggested using a URL, then yes—you should switch to using <iconURL>
instead of <iconblob>
.
<iconblob>
might be incorrect or not resolved during deployment.Using <iconURL>
ensures the image is loaded from a reliable external source and avoids packaging issues.
While Microsoft does not publish a full schema for the connector XML file, the following resources provide examples and guidance:
These resources describe the structure of the connector package, including the use of icon files and metadata.
Update your connector XML to use:
And remove or comment out the <iconblob>
reference. Make sure the image is publicly accessible and in a supported format (PNG or SVG).
Would you like help validating your connector XML or testing the icon rendering in a sandbox environment? I can also help you automate the packaging process to ensure consistency across environments.
🏷️ Tag me if you have any further questions or if the issue persists. ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems. ❤️ Give it a Like if you found the approach useful in any way.
this issue with custom connector icons disappearing in Power Automate after deployment is known and has been discussed in the Power Platform Community forums.
The icon image for a custom connector is typically referenced via a URL in the connector’s definition (OpenAPI/Swagger). Over time, this URL may become inaccessible due to:
When the image fails to load, Power Automate falls back to a generic icon — a plug or red dot depending on the designer version.
paconn
CLI."iconUrl": "https://yourdomain.com/images/connector-icon.png"
As noted in another thread , bundling the connector and connection references in the same solution can cause issues. Instead:
This ensures the connector is fully registered before the flows try to use it.
Tomac
986
Moderator
stampcoin
699
Super User 2025 Season 2
Riyaz_riz11
577
Super User 2025 Season 2