A client uses Dynamics 365 Sales, Power BI datasets, and Power BI dataflows. The Dynamics 365 Sales implementation has security roles that restrict data export. You need to ensure that data has the…

Question

Options

• AUse Microsoft Dataverse restrictions before setting up the Power BI reports.
• BLimit the role in Dynamics 365 Sales to only data allowed so it cannot be exported to Microsoft
• CLimit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365
• DShare Power BI dashboards only with users who are supported to see this data.

• A
  10% (3)
• B
  7% (2)
• C
  83% (25)

Explanation

C and D together create a layered defense: Option C enforces restrictions at the source by limiting Dynamics 365 Sales roles AND blocking Excel export, which closes the common backdoor where users bypass security by exporting raw data to a spreadsheet - both layers must be locked down together. Option D enforces restrictions at the consumption layer by ensuring Power BI dashboards are shared only with users authorized to see that data, maintaining consistent access control end-to-end.

Why A is wrong: Dataverse restrictions are a platform-level concern that doesn't directly enforce the same Dynamics 365 Sales role-based restrictions in Power BI - it operates at a different layer and doesn't solve the problem of dashboard-level access in Power BI.

Why B is wrong: Limiting roles in Dynamics 365 alone is insufficient because Power BI datasets and dataflows can pull and cache data independently; once data is in Power BI, D365 role restrictions no longer apply unless Power BI access is also controlled (which is what D addresses).

Memory tip: Think "lock the door at both ends" - C locks the source (D365 roles + no Excel export), D locks the destination (Power BI sharing). If you only lock one end, data can still leak through the other.

No community discussion yet for this question.