How to restrict Power BI links for the whole organisation

Turn organisation-wide links off, or allow them only for a security group, so reports are shared with the people who need them.

Every Microsoft 365 security check · Data Protection · NL-COL-021

What this check looks at

Checks the Power BI tenant setting that lets shareable links grant access to everyone in the organisation: whether anyone can make such a link, only named security groups, or no one.

Checks the Power BI tenant setting that lets shareable links grant access to everyone in the organisation: whether anyone can make such a link, only named security groups, or no one.

A link for specific people, or for people with existing access, keeps working with this off; only the "everyone in the organisation" option goes.

This check reads the setting through the Microsoft Fabric admin API. It passes when the setting is off, or on only for named security groups, and fails when it is on for the whole organisation. It needs the client’s Fabric administrator to allow service principals to use the read-only admin APIs; until then it shows as not checked, with the step to take.

Why it matters

A link that works for everyone in the organisation travels: forwarded in an email or pasted in a Teams channel, it opens the report for every member of staff, including people who should not see salaries, client margins or HR figures.

At an engineering firm, a finance analyst shared a salary-band report with a manager using an organisation-wide link, the default in the share dialogue. The manager forwarded it to the whole department to show the new bands, with every name and salary in it.

CIS Microsoft 365 Foundations Benchmark v7.0.0 recommendation 9.1.7 asks for this setting to be restricted. ISO 27001 A.5.15 (access control) and the NCSC 10 Steps data security guidance cover who can reach the organisation’s data.

How to fix it

Where: Microsoft Fabric admin portal → Tenant settings

Before you start

  • Find out who uses it on purpose and put them in a security group first, so restricting it does not stop work that is meant to happen.

Step by step

  1. Find who uses it. Ask the Power BI owners who relies on this, and make a security group for them in Entra, so restricting it does not stop work that is meant to happen.
  2. Restrict the setting. In the Microsoft Fabric admin portal, open Tenant settings → Export and sharing settings → Allow shareable links to grant access to everyone in your organisation. Turn it off, or set it to apply to specific security groups only, and select Apply.
  3. Review what was already shared. Restricting the setting stops it from now on. Ask the owners of shared reports and semantic models to check who already has access through it, and remove what is no longer needed.
  4. Confirm it. Reopen the setting to check it saved; Microsoft can take up to 15 minutes to apply it. The finding clears at the next assessment.

What users will notice

People outside the chosen group can no longer do this in Power BI; what was already shared stays shared until it is removed.

How to confirm it worked

The Fabric admin portal shows the setting off, or on for specific security groups only, and the next assessment passes.

Frameworks and controls

This check maps to controls in 12 frameworks. Passing it is evidence that the setting is in place, not a certification against any of them.

The frameworks and controls NL-COL-021 maps to
FrameworkControl
NCSC CAFB3.b Data in transit
DSPTStandard 1: Personal confidential data
Microsoft Cloud Security BenchmarkDP-2 Monitor anomalies and threats targeting sensitive data
Zero TrustData
SOC 2CC6.1 Logical access security software, infrastructure and architectures
NIST SP 800-1713.1.3 Control the flow of CUI in accordance with approved authorisations
CMMC Level 2AC.L2-3.1.3 Control CUI Flow
ISO 27001:2022A.5.15 Access controlA.5.14 Information transfer
CIS M3659.1.7 Ensure shareable links are restricted
CIS Controls v8.13.3 Configure data access control lists (IG1)
NIST CSF 2.0PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected
NCSC 10 StepsData security

The framework mappings were last checked against the published standards in October 2026.

Microsoft’s documentation

The full Microsoft 365 security checklist, worst first

ConfigCheckup

Check this in every tenant.

ConfigCheckup runs this check on every tenant you connect and gives you a step-by-step fix guide. The next assessment confirms the fix.

14 days of daily monitoring and alerts, every finding with its fix guide, and reports on up to 3 tenants, from your first connected tenant. No card. Then choose the plan that fits.Where this check fits: Microsoft 365 Copilot readiness assessment