🔒 Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided MS-102 Domain 3
Domain 3 — Module 7 of 8 88%
22 of 28 overall

MS-102 Study Guide

Domain 1: Deploy and Manage a Microsoft 365 Tenant

  • Establish and Configure Your M365 Tenant
  • Monitor Tenant Health and Network Readiness
  • Adoption Tracking and Microsoft 365 Backup
  • Manage Users, Contacts and External Identities
  • Groups, Shared Mailboxes and Licensing at Scale
  • Automate with PowerShell: Bulk User Operations
  • Roles, Role Groups and Workload Permissions
  • Delegate with Administrative Units and PIM

Domain 2: Implement and Manage Microsoft Entra Identity and Access

  • Prepare for Identity Synchronization
  • Implement Connect Sync and Cloud Sync
  • Monitor and Troubleshoot Identity Sync
  • Authentication Methods and Self-Service Password Reset
  • Password Protection and Authentication Troubleshooting
  • Entra Identity Protection and Risk Policies
  • Conditional Access and MFA Enforcement

Domain 3: Manage Security and Threats by Using Microsoft Defender XDR

  • Defender XDR: Security Posture and Threat Intelligence
  • Investigate Incidents with Advanced Hunting
  • Defender for Office 365: Threat Policies
  • Email Threats, Attack Simulation and Restricted Entities
  • Defender for Endpoint: Onboard and Protect
  • Vulnerability Management
  • Defender for Cloud Apps: Connect and Govern
  • Cloud App Discovery and Activity Monitoring

Domain 4: Manage Compliance by Using Microsoft Purview

  • Sensitive Information Types and Data Classification
  • Retention Labels and Data Lifecycle
  • Sensitivity Labels and Monitoring
  • DLP Policies Across M365 Workloads
  • Endpoint DLP and Alert Response

MS-102 Study Guide

Domain 1: Deploy and Manage a Microsoft 365 Tenant

  • Establish and Configure Your M365 Tenant
  • Monitor Tenant Health and Network Readiness
  • Adoption Tracking and Microsoft 365 Backup
  • Manage Users, Contacts and External Identities
  • Groups, Shared Mailboxes and Licensing at Scale
  • Automate with PowerShell: Bulk User Operations
  • Roles, Role Groups and Workload Permissions
  • Delegate with Administrative Units and PIM

Domain 2: Implement and Manage Microsoft Entra Identity and Access

  • Prepare for Identity Synchronization
  • Implement Connect Sync and Cloud Sync
  • Monitor and Troubleshoot Identity Sync
  • Authentication Methods and Self-Service Password Reset
  • Password Protection and Authentication Troubleshooting
  • Entra Identity Protection and Risk Policies
  • Conditional Access and MFA Enforcement

Domain 3: Manage Security and Threats by Using Microsoft Defender XDR

  • Defender XDR: Security Posture and Threat Intelligence
  • Investigate Incidents with Advanced Hunting
  • Defender for Office 365: Threat Policies
  • Email Threats, Attack Simulation and Restricted Entities
  • Defender for Endpoint: Onboard and Protect
  • Vulnerability Management
  • Defender for Cloud Apps: Connect and Govern
  • Cloud App Discovery and Activity Monitoring

Domain 4: Manage Compliance by Using Microsoft Purview

  • Sensitive Information Types and Data Classification
  • Retention Labels and Data Lifecycle
  • Sensitivity Labels and Monitoring
  • DLP Policies Across M365 Workloads
  • Endpoint DLP and Alert Response
Domain 3: Manage Security and Threats by Using Microsoft Defender XDR Premium ⏱ ~15 min read

Defender for Cloud Apps: Connect and Govern

Configure the Microsoft 365 app connector, create policies to detect risky behavior, and govern shadow IT with Microsoft Defender for Cloud Apps.

Governing what you can’t see

☕ Simple explanation

Defender for Cloud Apps is your organization’s air traffic control for cloud services.

Right now, your employees are using dozens — maybe hundreds — of cloud apps. Some you approved. Many you didn’t. You can’t secure what you don’t know about, and you can’t control what you haven’t connected.

Defender for Cloud Apps does three things: it discovers every cloud app your employees use (even the ones IT never heard of), it connects to your sanctioned apps (like Microsoft 365, Salesforce, Box) to monitor what’s happening inside them, and it enforces policies to block risky behavior automatically — like a user downloading 500 files in 10 minutes or sharing confidential documents with a personal email address.

Microsoft Defender for Cloud Apps (MDA) is Microsoft’s Cloud Access Security Broker (CASB). It provides visibility, control, and threat protection for cloud applications. Core capabilities:

  • Cloud Discovery — identifies all cloud apps in use via traffic log analysis or Defender for Endpoint integration
  • App connectors — API-level integration with sanctioned SaaS apps for deep visibility into user activities, files, and configurations
  • Policy engine — automated detection and response for risky activities, anomalous behavior, and compliance violations
  • Conditional Access App Control — real-time session controls that proxy traffic through Defender for Cloud Apps for inline monitoring and enforcement

MDA is included with Microsoft 365 E5, EMS E5, or available as a standalone license. It integrates natively with Entra ID, Defender for Endpoint, and the broader Defender XDR suite.

App connectors — your eyes inside SaaS apps

App connectors use API-level integration to pull activity data, user information, and file metadata from connected cloud applications. Once connected, you get deep visibility without proxying traffic.

Connecting Microsoft 365

The Microsoft 365 connector is the first one every admin should configure. It provides visibility into:

  • Exchange Online — mail forwarding rules, delegate access, mailbox permission changes
  • SharePoint Online — file sharing, external access, permission changes
  • OneDrive — file downloads, sharing with external users, sync activity
  • Teams — guest access, app installations, file sharing in channels
  • Power Platform — Power Automate flows, Power Apps usage

To connect Microsoft 365:

  1. Navigate to Settings in the Defender portal, then Cloud Apps, then Connected apps, then App Connectors
  2. Select Microsoft 365 from the app catalog
  3. Choose which Microsoft 365 components to connect (Exchange, SharePoint, Teams, etc.)
  4. Authorize the connection using a Global Administrator account
  5. The connector begins pulling historical data — initial sync can take several hours

Third-party app connectors

Beyond Microsoft 365, Defender for Cloud Apps connects to popular SaaS platforms via API connectors:

AppKey visibilityAuthentication method
SalesforceUser logins, data exports, permission changesOAuth connected app
BoxFile sharing, external collaboration, admin actionsEnterprise app authorization
Google WorkspaceDrive sharing, email forwarding, admin console changesService account with domain-wide delegation
DropboxFile sharing, link permissions, team folder accessTeam admin authorization
ServiceNowInstance access, configuration changes, data exportsOAuth or username/password
ℹ️ Priya discovers shadow IT at GlobalReach

When Priya first connected the Microsoft 365 connector at GlobalReach Corp, she expected to find normal activity. Instead, the first week revealed:

  • 47 mail forwarding rules routing email to external addresses — three belonged to former employees whose accounts were never properly offboarded
  • 2,100 externally shared files in OneDrive — including 340 marked as “anyone with the link” (no authentication required)
  • 14 Power Automate flows copying SharePoint data to personal Dropbox accounts

Without the app connector, none of this was visible. The M365 admin center shows some of this data in scattered reports, but Defender for Cloud Apps surfaces it through a unified policy engine that can detect and respond automatically.

Policy types — automated detection and response

Policies are the enforcement engine. Each policy type addresses a different threat vector.

Defender for Cloud Apps Policy Types
FeatureWhat It MonitorsExample Use Case
Activity policyUser and admin activities from connected appsAlert when a user downloads more than 100 files in 5 minutes
Anomaly detection policyBehavioral deviations detected by ML (built-in, always on)Impossible travel — user signs in from London and Tokyo within 30 minutes
File policyFiles stored in connected cloud appsAlert when a file containing credit card numbers is shared externally
Access policyReal-time sign-in events via Conditional Access App ControlBlock access to Exchange from unmanaged devices
Session policyReal-time in-session actions via Conditional Access App ControlAllow viewing but block downloading sensitive files from unmanaged devices

Activity policies — monitoring what users do

Activity policies trigger when specific user or admin actions match your criteria. You define:

  • Activity filter — app, user, IP address, location, activity type
  • Repeated activity — trigger only when the same activity occurs X times within a timeframe
  • Alert severity — Low, Medium, High
  • Governance action — what happens when the policy triggers (notify user, suspend user, require sign-in again)

Example: Priya creates a policy at GlobalReach to detect mass downloads.

SettingValue
Activity typeDownload file
Repeated activityMore than 50 times within 5 minutes
App filterSharePoint Online, OneDrive
Alert severityHigh
Governance actionSuspend user, notify admin

Anomaly detection policies — ML-powered threat detection

These are built-in policies that run automatically — no configuration needed to start. They use machine learning to establish behavioral baselines for each user and alert when deviations occur.

Key built-in anomaly detections:

DetectionWhat it catches
Impossible travelSign-ins from geographically distant locations within an impossible timeframe
Activity from infrequent countrySign-in from a country the user has never accessed from before
Ransomware activityFile extension patterns and activity sequences matching ransomware behavior
Multiple failed login attemptsBrute force patterns against cloud applications
Unusual file share activitySharing patterns that deviate significantly from the user’s baseline
Unusual admin activityAdmin actions that don’t match normal patterns

You can tune anomaly policies (adjust sensitivity, exclude groups) but you cannot create new ones from scratch.

File policies — protecting sensitive content

File policies scan files stored in connected apps for sensitive content, risky sharing configurations, or policy violations.

  • Content inspection — scans file contents for sensitive data types (credit cards, health records, personally identifiable information)
  • Sharing status — detects files shared externally, publicly, or with specific domains
  • File type — filters by extension, size, or modification date
  • Governance actions — remove external sharing, quarantine file, notify file owner, apply sensitivity label

Access and session policies — real-time inline control

These two policy types require Conditional Access App Control — a Conditional Access integration that routes user sessions through a reverse proxy for real-time monitoring and enforcement.

Access Policies vs Session Policies
FeatureAccess PolicySession Policy
When it evaluatesAt sign-in timeDuring the active session
What it controlsWhether the user can access the app at allWhat the user can do inside the app
Example actionBlock sign-in from unmanaged devicesAllow viewing files but block download or print
Requires Conditional Access integrationtruetrue
GranularityBinary — allow or block accessAction-level — control specific operations within the session
💡 Exam tip: Which policy type for which scenario

The exam describes a scenario and expects you to identify the correct policy type:

  • “Alert when a user shares a file containing PII externally” — File policy (content inspection + sharing filter)
  • “Block downloads from unmanaged devices” — Session policy (requires CAAC, controls in-session actions)
  • “Detect a user signing in from two countries simultaneously” — Anomaly detection policy (impossible travel, built-in)
  • “Alert when an admin performs bulk user deletions” — Activity policy (monitors specific admin actions)
  • “Prevent access to Salesforce from non-corporate networks” — Access policy (evaluates at sign-in)

The key differentiator: if the scenario involves content inspection or file sharing, it’s a file policy. If it involves what happens during a session (download, print, copy), it’s a session policy. If it involves user behavioral anomalies, it’s anomaly detection.

Alert management — investigating and responding

When a policy triggers, it generates an alert in the Defender portal. Investigation workflow:

  1. Triage — review alert severity, affected user, and triggered policy
  2. Investigate — examine the activity log for context (what else did this user do before and after the alert?)
  3. Determine scope — is this an isolated incident or part of a broader attack?
  4. Respond — apply governance actions (suspend account, revoke sessions, remove sharing)
  5. Resolve — mark the alert as true positive (confirmed threat), false positive (benign), or benign true positive (real but not risky)

Governance actions

Governance actions are the automated or manual responses available when investigating alerts:

ActionWhat it does
Notify userSends an email notification to the affected user
Suspend userDisables the user account in the connected app
Require sign-in againRevokes active sessions, forcing re-authentication
Remove collaboratorRemoves specific external sharing from a file
Put in quarantineMoves the file to a quarantine folder and removes sharing
Apply sensitivity labelApplies a Microsoft Purview sensitivity label to the file
Question

What is the difference between an activity policy and an anomaly detection policy?

Click or press Enter to reveal answer

Answer

Activity policies are custom rules you create — you define exact conditions (e.g., more than 50 downloads in 5 minutes). Anomaly detection policies are built-in ML models that learn each user's behavioral baseline and alert on deviations (e.g., impossible travel, unusual admin activity). You can tune anomaly policies but cannot create new ones. Activity policies require manual configuration.

Click to flip back

Question

What is Conditional Access App Control and which policy types require it?

Click or press Enter to reveal answer

Answer

Conditional Access App Control (CAAC) routes user sessions through a reverse proxy in Defender for Cloud Apps, enabling real-time monitoring and enforcement. Access policies (control sign-in decisions) and session policies (control in-session actions like download, print, copy) both require CAAC. Activity policies and file policies do NOT require CAAC — they use API connector data.

Click to flip back

Question

What must you use to connect Microsoft 365 to Defender for Cloud Apps?

Click or press Enter to reveal answer

Answer

The Microsoft 365 app connector — configured in the Defender portal under Settings, then Cloud Apps, then Connected apps, then App Connectors. Requires Global Administrator authorization. You select which M365 components to connect (Exchange, SharePoint, OneDrive, Teams, Power Platform). The initial data sync takes several hours.

Click to flip back

Question

Name the five policy types in Defender for Cloud Apps.

Click or press Enter to reveal answer

Answer

1) Activity policy — monitors user and admin actions. 2) Anomaly detection policy — ML-based behavioral analysis (built-in). 3) File policy — scans file content and sharing. 4) Access policy — controls sign-in via CAAC proxy. 5) Session policy — controls in-session actions (download, print) via CAAC proxy.

Click to flip back

Question

What governance action would you use to immediately prevent a compromised user from accessing cloud apps?

Click or press Enter to reveal answer

Answer

Revoke sessions (Require sign-in again) for immediate effect — this invalidates all active tokens so existing sessions stop working. Then suspend the user account in the connected app to prevent new sign-ins. Revoking sessions alone doesn't prevent re-authentication if credentials are compromised, so both actions together provide full containment.

Click to flip back

Knowledge check

Knowledge Check

Priya configures a file policy in Defender for Cloud Apps to detect files containing health records shared externally from SharePoint Online. The policy is configured with content inspection enabled and governance set to 'Remove external sharing.' A GlobalReach HR manager shares a benefits document containing employee health information with an external insurance broker via a SharePoint sharing link. What happens?

Knowledge Check

Elena wants to prevent MedGuard Health staff from downloading patient records from SharePoint Online when accessing from personal (unmanaged) devices — but she still wants them to be able to view the documents in the browser. Which policy type should she configure?

Knowledge Check

Marcus has connected Microsoft 365 to Defender for Cloud Apps at Oakwood Financial. He receives an anomaly detection alert: 'Impossible travel — user JSmith signed in from New York at 09:00 and from Singapore at 09:15.' JSmith confirms they are in New York and did not travel. What should Marcus do?

🎬 Video coming soon


Next up: Cloud App Discovery and Activity Monitoring — discover unsanctioned apps across your organization and investigate risky usage patterns.

← Previous

Vulnerability Management

Next →

Cloud App Discovery and Activity Monitoring

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.