Power BI Azure Maps: Add custom GeoJSON boundaries

Key insights

• Add the GeoJSON file as a reference layer in the Azure Maps visual's Format pane.
• Reference-layer boundaries remain visible when report data is filtered with a slicer.
• Use latitude and longitude fields to plot individual locations and a measure such as sales to size the points.
• The demonstration describes filtered data reloading relevant points beyond the 30,000-point rendering limit.
• The demonstrated map reframes to filtered locations, including when filtering or cross-highlighting from other visuals.

Power BI’s Azure Maps visual can display custom GeoJSON boundaries as a reference layer alongside report data, so users can view locations in the context of territories or other organization-specific regions. This is useful for report authors and analysts whose operational areas do not match standard geographies such as states. Pragmatic Works demonstrates the workflow with a fictional customer-sales report and a U.S. states GeoJSON file.

What it does

GeoJSON is a file format for geographic features, including points, lines, and polygons. A polygon can represent an area such as a state, sales territory, school district, service area, or delivery zone. In Power BI, the Azure Maps reference layer places those boundaries on the map while fields from the report’s data provide the locations and measures being analyzed.

In the demonstration, the report uses customer records with latitude, longitude, and sales data. The boundary layer is a separate geographic overlay: filtering the customer data to a state does not remove the other state outlines. That distinction lets a reader examine filtered locations against a broader geographic frame.

The demonstrated reference layer is used to show boundaries, not to replace the report’s customer data. The example also compares Azure Maps with Shape Map: the presenter’s point is that Azure Maps can show region polygons and separate data points together in the same visual.

Who it is for and what you need

This workflow is aimed at Power BI report authors working with geographic data that needs custom boundaries. You need an Azure Maps visual, a GeoJSON file containing the boundaries you want to display, and report data with location information. The example uses latitude and longitude to plot customers and state values to filter them.

For an organization’s own geography, the file must represent the intended areas, such as sales territories or service regions. The presenter notes that the shapes need a value that can match the geographic feature to the Power BI data. The demonstration uses state names; it does not give a detailed data-preparation or matching configuration.

The provided material does not state licensing prerequisites, tenant or regional availability, or whether an administrator must enable the Azure Maps visual. It also does not establish a rollout status for the September 2026 behaviors beyond the presenter describing them as improvements in that Power BI release.

How it works

1. Add an Azure Maps visual to the report. In the visual’s formatting options, open Reference layer and load the GeoJSON file. The Microsoft documentation linked below covers adding a reference layer.

2. Add location fields to the visual. In the example, the author first uses state data to make the boundaries easy to see, then replaces that field with latitude and longitude to plot customer locations. If Power BI aggregates a coordinate field, set it to Don’t summarize.

3. Add a measure such as sales to the visual’s Size field if point size should represent that measure. A state slicer can then narrow the customer data; the reference-layer boundaries remain on the map while the data points respond to the selection.

4. Use the reference-layer formatting options to adjust polygon fill and border colors, border transparency, and border width. The demonstration also shows conditional color formatting and controls for unmapped objects and custom colors.

With a large dataset, filtering can change which points the visual displays. Pragmatic Works demonstrates a 50,000-record example and describes a 30,000-point rendering limit. In the presenter’s comparison, filtering previously could leave relevant points out if they were not part of the initial loaded subset; the demonstrated improvement reloads points relevant to the filter.

The demonstration also shows the map automatically reframing around the filtered area. The presenter says this behavior can occur with slicers, filters, and cross-highlighting from other report visuals, so users do not have to manually pan to the selected region.

Limitations and open questions

A reference layer does not automatically make a report’s business data geographically meaningful: the report still needs usable location fields, and custom boundaries need to correspond to the areas the organization wants to analyze. The demonstration does not provide a full GeoJSON authoring or validation guide, nor does it specify file-size limits or troubleshooting steps for malformed boundary files.

The source describes the point-rendering limit and the newer filtering behavior through one example. It does not provide independent performance testing or details on how the behavior varies with other dataset sizes. The 30,000-point figure and the September 2026 change should therefore be read as claims demonstrated by the presenter, not as a complete specification.

For teams deciding between visuals, the demonstrated distinction is practical: use the Azure Maps reference layer when you want boundaries and separate report data points visible together. The material does not give a full feature-by-feature comparison with Shape Map or cover every supported reference-layer file type.

Sources

• Microsoft documentation on adding an Azure Maps reference layer
• Pragmatic Works demonstration of GeoJSON boundaries in Power BI Azure Maps

Frequently asked questions

How do I add GeoJSON boundaries to Azure Maps in Power BI?

In the Azure Maps visual’s formatting options, open Reference layer and load the GeoJSON file. Add the report’s location fields to the visual to show data alongside the boundaries.

Do Azure Maps reference-layer boundaries respond to slicers?

In the demonstrated setup, the customer data points respond to the state slicer, but the reference-layer boundaries remain visible. The layer supplies geographic context rather than being filtered like the plotted data.

What does the 30,000-point limit mean for filtered maps?

The demonstration describes a 30,000-point rendering limit and says the September 2026 Power BI improvement reloads points relevant to a filter, even when they were not in the initial subset.

What license or Power BI version is required for GeoJSON reference layers?

The provided material does not specify licensing requirements or a minimum Power BI version. It also does not state tenant-wide or regional availability.