Publishing and sharing

There are two ways to get a map in front of an audience: share it inside Fabric, or publish a view-only version you can embed anywhere.

Sharing inside Fabric

Because an Icon Map is a native Fabric item, you can Share it using Fabric's standard sharing — grant colleagues access and they open the live map in the workload, in reading view or edit mode depending on their permission.

Publishing a map

Publish (from the ribbon) freezes the map into an immutable, view-only published version that can be embedded in your own websites, apps, and portals — similar in spirit to Power BI's "Publish to web", but staying within your tenant's storage.

Snapshot or live data

When you publish, you choose how the data behaves:

  • Snapshot — the data is frozen at publish time. The published map is static and is the safest option.
  • Live — viewers run the map's pinned queries each time they load it, so the map reflects current data. Live publishes let you set query budgets (a default of 500 fresh queries per day and 50,000 rows per query) and opt individual sources out of live querying.

Access controls

You control who can open a published map:

  • An anonymous link (with an explicit acknowledgement when combining anonymous access with live data),
  • Signed embed tokens, and
  • An allowed-origins allow-list restricting which sites may host the embed.

You can also choose whether to offer bookmarks and which map controls viewers get.

Where the data lives

Publishing writes the map's configuration and data into your own OneLake, under a Files/_published/ folder in the workspace. Your data never leaves your tenant. See Security & permissions for the access a published map requires.

Managing published maps

You can list your published maps, revoke a link at any time, and re-publish to refresh the snapshot (which produces a new link).

Organizations that don't want maps embedded outside Fabric at all can have publishing disabled for their tenant, or for individual workspaces: the Publish action disappears from the editor and the embed service refuses to serve the affected maps, including ones published before the change. Contact your Icon Map onboarding contact to configure this.

Next steps