What are the recommended practices for securing data sharing with external customers in Fabric?

• A. Use least privilege access, data masking for PII, authentication, auditing, revocation processes, and sandbox environments.
• B. Open access to all shared datasets for all external customers.
• C. Rely solely on encryption at rest; ignore auditing.
• D. Disable authentication to speed up sharing.

Answer: (A)

Securing data sharing with external customers in Fabric relies on combining strong identity, strict access control, data protection, and ongoing visibility. Granting the minimum necessary rights (least privilege) ensures external users can do what they need without seeing or altering more data than required. Masking data elements that contain personally identifiable information keeps sensitive details hidden even when users have broader access. Requiring solid authentication verifies who is connecting, and maintaining thorough auditing creates a detailed record of who accessed what and when, enabling monitoring, compliance reporting, and incident response. Clear revocation processes let you instantly cut off access when a contract ends, a policy changes, or a security issue arises. Sandbox environments provide isolated spaces for external workloads, allowing testing and data exploration without impacting production data or systems. Together, these practices create a secure, controllable, and auditable external-sharing model. Open access undermines privilege controls; encryption at rest handles data only while stored and does not address access, usage, or monitoring; and disabling authentication eliminates identity verification entirely, which is unsafe.