Data, privacy, and residency

Icon Map for Fabric is designed to work on your data, in your tenant — a principle that runs through every part of the product.

Your data stays in your tenant

  • Icon Map reads your data in place from OneLake and your Fabric sources — it doesn't copy or move your data to build a map.
  • When you publish a map, the frozen configuration and any data snapshot are written to your own OneLake (under a Files/_published/ folder), not to Tekantis infrastructure. Your data never leaves your tenant.
  • Write-back edits are saved back into your OneLake (an annotations store or a layer file).

Identity and access

Icon Map acts using your Microsoft Entra identity and inherits your Fabric permissions, so it can only ever reach data you're already entitled to see. Access to layers and catalogs is governed by the same Fabric and OneLake permissions you use elsewhere — including row-level security on Power BI semantic models. See Security & permissions configuration for the specifics.

Hosted services

Some parts of the experience are hosted by Tekantis — for example, the basemap catalog, the public Icon Map Catalog tiles, and the embedded viewer endpoint. These serve map styling and published, view-only content; they don't hold your source Fabric data.

Compliance resources

For formal security and compliance material, see:

Next steps