Which combination of actions should you enable to enable external tools to create Fabric items and access XMLA while following least privilege?

• A. Enable XMLA Endpoints and Analyze in Excel with on-premises datasets Enabled; XMLA Endpoint Read Write; Users can create Fabric items Enabled.
• B. Enable Analyze in Excel; XMLA Endpoint Read Only; Users can create Fabric items Enabled.
• C. Enable XMLA Endpoints; Capacity: XMLA Read Only; Enable Users editing.
• D. Enable XMLA Endpoints; Publish to Web; Users can create Fabric items.

Answer: (A)

The key idea is to give external tools a controlled bridge into Fabric and permit only the actions those tools actually need, avoiding wider exposure. Enabling XMLA Endpoints creates the gateway external clients use to query and manage Fabric items. Providing XMLA Endpoint Read Write gives those tools the necessary capability to read data and also create or modify items as part of their workflow, which is essential when external tools are used to build new Fabric items rather than just consume them. Pairing that with Analyze in Excel and on-premises datasets enables a common, secure outside-in analysis workflow—Excel can connect to Fabric through XMLA and work with on-prem data sources, aligning with standard external-tool usage without opening up broader, online access. Finally, allowing users to create Fabric items ensures users can publish and manage their own items rather than needing elevated roles or an admin to do it for them, staying within a least-privilege model.

The other options either limit needed capabilities or introduce broader exposure. For example, making XMLA read-only prevents item creation via external tools; enabling only on-prem analysis without the associated XMLA permissions or item-creation rights would hinder the intended workflow; publishing to the web would expose Fabric items publicly, which conflicts with least privilege.