Fabric Admin Portal Settings for Direct Lake XMLA
You have a Fabric tenant that contains a workspace named Workspace1. Workspace1 is assigned to a Fabric capacity. You need to recommend a solution to provide users with the ability to create and publish custom Direct Lake semantic models by using external tools. The solution must follow the principle of least privilege. Which three actions in the Fabric Admin portal should you include in the recommendation? Each correct answer presents part of the solution. NOTE: Each correct answer is worth one point.
Community Votes
100% of anonymous learners picked answer ADE. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the specific prerequisites for using external tools with Direct Lake: enabling the XMLA endpoint at both tenant and capacity levels, plus allowing item creation. The common trap is selecting 'Edit data models in Power BI service', which explicitly excludes Direct Lake.
To allow external tools to create and publish custom Direct Lake semantic models with least privilege, you must enable tenant-level XMLA access, capacity-level Read/Write XMLA endpoints, and user creation permissions. This configuration ensures secure model management via external clients like Tabular Editor.
Candidates often select option C ('Users can edit data model in the Power BI service') because it sounds relevant to editing models. However, Microsoft documentation explicitly states this setting does not apply to Direct Lake semantic models or editing through XMLA/APIs.
Community Discussion (22 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
To enable external tools (like SSMS or Tabular Editor) to manage Direct Lake models, three distinct settings are required. First, Allow XMLA Endpoints (Option A) must be enabled in Tenant Settings to permit any XMLA traffic from external clients. Second, XMLA Endpoint (Option D) must be set to Read Write in Capacity Settings; without this, even if enabled, users would only have read-only access, preventing publishing. Third, Users can create Fabric items (Option E) must be enabled in Tenant Settings because creating a new semantic model constitutes creating a new Fabric item.Why the Other Options Are Wrong
Option B allows guest users access, which violates the principle of least privilege as it broadens access beyond necessary internal users. Option C allows editing within the Power BI Service browser interface, but the documentation explicitly states: "This setting doesn't apply to DirectLake semantic models or editing a semantic model through an API or XMLA endpoint." Therefore, it does not solve the requirement for external tool usage.Community Comment Notes
Community consensus strongly supports ADE. Commenters note that Option C is incorrect because the setting description explicitly excludes Direct Lake. Several users reference official Microsoft Learn links confirming that XMLA Read/Write is mandatory for publishing and that 'Create Fabric items' is needed to generate new models externally.Official Reference
Exam Strategy
Always distinguish between 'editing in the service' and 'editing via XMLA'. For Direct Lake, rely on XMLA settings. Remember that 'creating' a model requires 'create item' permissions, while 'modifying' requires 'read/write' XMLA access.
Frequently Asked Questions
Why is Option C wrong for Direct Lake models?
The 'Users can edit data model in the Power BI service' setting explicitly excludes Direct Lake models and XMLA-based editing according to Microsoft documentation.
Why do we need both Tenant and Capacity XMLA settings?
Tenant settings (A) enable the feature globally, while Capacity settings (D) define the permission level (Read/Write). Both are required for external tools to publish changes.
Related Analysis
Practice All DP-600 Questions
Access 115 questions with complete answers and detailed explanations.
View Full DP-600 Practice Test →