Question 53 — AB-650 Case Study Set
Business Context
Paideffort uses Microsoft 365 for approximately 8,400 employees. The Finance division exchanges documents with external auditors through email, Microsoft Teams channels, SharePoint document libraries, and shared OneDrive folders. Finance recipients are already protected by custom anti-phishing, anti-spam, anti-malware, Safe Attachments, and Safe Links policies. Security administrators previously treated those recipient-scoped configurations as the primary protection boundary for Finance.
The security requirement is that files uploaded directly to Microsoft Teams, SharePoint, or OneDrive receive malware protection even when the files never travel through Exchange mail flow. If a file is identified as malicious, users must be prevented from obtaining a local copy, while administrators must still be able to support removal of the malicious content.
Current Collaboration Environment
Finance employees use a Teams team named Finance Operations. Files posted to its channels are stored in Microsoft 365 collaboration storage. The department also maintains Finance-Audit in SharePoint and shares selected working documents through OneDrive.
A pilot group called Finance-Protected contains 180 users. Security engineers attempted to extend collaboration-file protection only to this group because other departments have not yet completed communications for the rollout.
The Microsoft Defender portal currently shows the tenant-level option for Defender for Office 365 protection across SharePoint, OneDrive, and Microsoft Teams as disabled. The Finance mail-flow threat policies remain enabled and continue protecting messages addressed to Finance users.
Governance Configuration
Paideffort's desired-state configuration service currently stores the following record:
collaborationProtection:
targetGroup: Finance-Protected
teams: enabled
sharePoint: disabled
oneDrive: disabled
safeAttachments: enabled
The automation team also maintains a JSON record used to validate malicious-file controls:
{
"defenderCollaborationProtection": true,
"maliciousFileOpenBlocked": true,
"maliciousFileMoveBlocked": true,
"maliciousFileCopyBlocked": true,
"maliciousFileShareBlocked": true,
"maliciousFileDeleteAllowed": true
}
Operational Validation
During testing, an external auditor uploads an infected spreadsheet directly to the Finance Operations Teams channel rather than emailing it. The existing Finance anti-malware mail policy does not inspect the upload. After collaboration protection is enabled in a test tenant, Defender identifies the file as malicious. Users can no longer open, move, copy, or share it through Microsoft 365, but the validation team confirms that a download action remains available.
One engineer proposes creating separate Defender configurations for Teams, SharePoint, and OneDrive and applying each only to Finance-Protected. Another engineer proposes completing the rollout through a tenant setting and a SharePoint Online PowerShell configuration before expanding testing beyond Finance.
Safe Links Policy State
The tenant contains the following Safe Links assignments:
FinanceDirectors:
presetPolicy: Strict
FinanceEmployees:
presetPolicy: Standard
FinanceCustomLinks:
priority: 0
RemainingUsers:
policy: BuiltInProtection
Paideffort plans to expand collaboration protection throughout the organization. Governance reports must distinguish mail-flow protections from collaboration-surface protection, identify whether malicious-file downloads are blocked, and avoid representing a recipient-scoped policy as though it controls the tenant-wide collaboration setting.