M365 Tenant Configuration & AI Services Licensing
AB-650 Exam Alignment
AB-650
Domain 1 — Configure and manage a Microsoft 365 tenant: configure branding in a Microsoft 365 tenant including logo, company URL, themes, and backgrounds; implement and manage domains; configure and manage organizational settings including security and privacy settings and the organization profile; manage and monitor Microsoft 365 licenses including group-based licensing and pay-as-you-go; manage and monitor licenses for AI services including Microsoft 365 Copilot, Microsoft Agent 365, and Microsoft Copilot Studio; configure and use Microsoft 365 Backup including setup, restore, and monitor; configure and review network connectivity insights; monitor the health of Microsoft 365 services by using Service health including notification configuration.
- Know the M365 Admin Center URL: admin.microsoft.com and each AI-specific sub-section (Copilot, Agent settings)
- Distinguish between standard M365 licences and AI services licences (Copilot, Agent 365, Copilot Studio)
- Know the Microsoft 365 Backup products: Exchange Online (up to 1 year), SharePoint Online (up to 1 year), and OneDrive (up to 1 year)
- Understand group-based licensing for bulk assignment of AI service licences
- Know Network Connectivity Insights location in admin center and what metrics it surfaces
🏠 The Microsoft 365 Admin Center for AB-650
The Microsoft 365 Admin Center at admin.microsoft.com is the primary management console for all AB-650 administrative tasks. For AB-650 candidates, the admin center has expanded significantly beyond the MS-102 era — it now includes dedicated sections for Copilot, Agent settings, and AI services licensing that form the foundation of Domain 3.
🆓 Tenant Branding
Tenant branding in Microsoft 365 controls how the sign-in experience and administrative interfaces appear to users across the organisation. Configured under Settings → Org settings → Organization profile, branding settings apply globally to the Microsoft 365 sign-in page and Microsoft Entra ID authentication flows.
Configurable Branding Elements
| Branding Element | Where It Appears | Max Size / Format |
|---|---|---|
| Company logo (banner) | Sign-in page header, M365 app launcher, Entra ID sign-in flow | 280 × 60px, max 10 KB, PNG or JPEG |
| Company logo (square) | Sign-in page (mobile), M365 tiles | 240 × 240px, max 10 KB, PNG or JPEG |
| Background image | Sign-in page background (replaces the default Microsoft blue pattern) | 1920 × 1080px, max 300 KB, PNG or JPEG |
| Background colour | Sign-in page background when no image is set — hex colour code | Hex colour code (e.g. #0a2a70) |
| Sign-in page text | Custom text below the sign-in box (e.g. IT support contact details, policies) | Max 256 characters |
| Company name | Displayed in M365 admin center, user-facing messages, support tickets | Max 64 characters |
| Company URL (technical contact) | Shown in Microsoft 365 support pages and self-service articles | Valid URL, max 1024 characters |
⚠️ Branding vs Microsoft Entra ID Custom Branding
The M365 Admin Center branding (Settings → Org settings → Organization profile) sets the tenant-wide default. Microsoft Entra ID Custom Branding (Entra admin center → User experiences → Company branding) provides per-locale overrides and more granular control including custom CSS, custom sign-in texts, and username hint text. AB-650 tests both — the M365 Admin Center path is Domain 1 (this module); Entra branding is Domain 2 (Module 3).
🌐 Custom Domains
Every Microsoft 365 tenant starts with a default .onmicrosoft.com domain. Custom domains (e.g. contoso.com) are added so that users have professional email addresses and SharePoint URLs. Custom domain management is at Settings → Domains.
Domain Verification Process
| DNS Record | Service | Example Value |
|---|---|---|
| MX | Email delivery to Exchange Online | contoso-com.mail.protection.outlook.com (priority 0) |
| TXT (SPF) | Sender Policy Framework — prevents email spoofing | v=spf1 include:spf.protection.outlook.com -all |
| CNAME (Autodiscover) | Outlook automatic configuration | autodiscover.outlook.com |
| CNAME (Teams) | Skype for Business / Teams federation | sipdir.online.lync.com |
| TXT (DKIM) | DomainKeys Identified Mail — email signing | Generated by Exchange Online (Module 5) |
🔒 Organizational Settings — Security & Privacy
Organisational settings at Settings → Org settings and Settings → Security & privacy control tenant-wide defaults for user behaviour, authentication, and data handling. These settings apply to all users unless overridden by policies at the user or group level.
Key Security & Privacy Settings
| Setting | Location | What It Controls | AB-650 Relevance |
|---|---|---|---|
| Password expiration policy | Security & privacy → Password expiration policy | Whether passwords expire and after how many days. Microsoft recommends setting passwords to never expire when combined with MFA | Domain 2 (authentication) — tested with SSPR and MFA scenarios |
| Self-service password reset | Security & privacy → Password reset | Enable SSPR for users to reset their own passwords without contacting IT | Domain 2 (Module 4) — detailed Entra SSPR config |
| Idle session timeout | Security & privacy → Idle session timeout | Signs out users from Microsoft 365 web apps after a specified period of inactivity (15 min to 24 hours) | Domain 1 — tenant-level security hardening |
| Privacy profile | Org settings → Organization profile → Privacy statement URL | Link to your organisation’s privacy statement shown to users in M365 apps | Domain 1 — organisational profile configuration |
| User-owned apps and services | Org settings → Services → User owned apps and services | Whether users can access Office Store apps, start Teams trials, or acquire third-party apps without admin approval | Domain 1 — controls self-service purchase behaviour for AI services |
| Cortana integration | Org settings → Services → Cortana | Enable or disable Cortana in Microsoft 365 for the tenant — distinct from Copilot settings | Domain 1 — legacy AI service; separate from M365 Copilot |
🌟 AI Services Licensing NEW IN AB-650
This is the most significant new Domain 1 topic for AB-650 candidates. Managing licences for AI services requires understanding three distinct Microsoft AI products — each with its own licensing model, prerequisites, and capabilities. These are managed at Billing → Licences and Billing → Your products in the M365 Admin Center.
The Three AB-650 AI Service Licences
| Product | Licence Name | What It Enables | Prerequisites |
|---|---|---|---|
| Microsoft 365 Copilot | Microsoft 365 Copilot (per-user add-on) | Copilot in Word, Excel, PowerPoint, Outlook, Teams, Loop, OneNote; Copilot Chat (work mode); Microsoft 365 Copilot Search | Eligible base M365 licence (E3, E5, Business Premium, F3+); Exchange Online mailbox; M365 Apps on Current Channel |
| Microsoft Agent 365 🔥 | Microsoft Agent 365 (per-user or capacity) | Access to the Agent 365 platform — deploy, manage, and interact with AI agents registered in the agent registry; agent identity lifecycle via Entra Agent ID | Microsoft 365 Copilot licence; Microsoft Entra ID P1 or P2 for Conditional Access on agents |
| Microsoft Copilot Studio | Copilot Studio (per-user or message-capacity) | Build and publish custom AI agents and declarative agents; agent flows; agent analytics; access to Copilot Studio portal (copilotstudio.microsoft.com) | Microsoft 365 licence (E1+); Power Platform environment; no M365 Copilot licence required to build agents (only to deploy into M365 Copilot) |
🔥 Microsoft Agent 365 — Completely New in AB-650
Microsoft Agent 365 is a brand-new platform (launched 2026) that represents the biggest new topic in AB-650 vs MS-102. It is the enterprise management layer for AI agents — allowing admins to control which agents users can access, monitor agent activity, protect sensitive data accessed by agents, and manage agent identities via Microsoft Entra Agent ID. Agent 365 is covered in depth in Module 8, but you need to know its licensing model in Module 1 since Domain 1 of the AB-650 exam explicitly tests “manage and monitor licenses for AI services, including Microsoft Agent 365.”
Group-Based Licensing for AI Services
Group-based licensing allows you to assign AI service licences to a Microsoft Entra security group or Microsoft 365 group rather than individual users. When a user is added to the group, the licence is automatically assigned. When removed, the licence is automatically reclaimed. This is the recommended approach for scaling Copilot rollouts to hundreds or thousands of users.
Connect-MgGraph -Scopes "User.ReadWrite.All","Group.ReadWrite.All","Directory.ReadWrite.All" # Get all available SKUs including AI service licences Get-MgSubscribedSku | Select-Object SkuPartNumber,SkuId,ConsumedUnits,@{N="Available";E={$_.PrepaidUnits.Enabled - $_.ConsumedUnits}} | Sort-Object SkuPartNumber | Format-Table -AutoSize # Find the Microsoft 365 Copilot licence SKU ID $CopilotSku = Get-MgSubscribedSku | Where-Object {$_.SkuPartNumber -eq "Microsoft_365_Copilot"} Write-Host "Copilot SKU ID: $($CopilotSku.SkuId) | Available: $($CopilotSku.PrepaidUnits.Enabled - $CopilotSku.ConsumedUnits)" # Assign Copilot licence to a single user $UserId = (Get-MgUser -Filter "UserPrincipalName eq 'alice@contoso.com'").Id Set-MgUserLicense -UserId $UserId -AddLicenses @{SkuId = $CopilotSku.SkuId} -RemoveLicenses @() # Assign AI service licence to a group (group-based licensing) $GroupId = (Get-MgGroup -Filter "DisplayName eq 'Copilot-Pilot-Users'").Id Set-MgGroupLicense -GroupId $GroupId -AddLicenses @{SkuId = $CopilotSku.SkuId} -RemoveLicenses @() # Get all Copilot-licensed users Get-MgUser -All -Property DisplayName,UserPrincipalName,AssignedLicenses | Where-Object {$_.AssignedLicenses.SkuId -contains $CopilotSku.SkuId} | Select-Object DisplayName,UserPrincipalName | Format-Table -AutoSize # Check for group-based licensing assignment errors Get-MgGroupMemberWithLicenseError -GroupId $GroupId | Select-Object DisplayName,UserPrincipalName | Format-Table -AutoSize
💾 Microsoft 365 Backup NEW IN AB-650
Microsoft 365 Backup is a native Microsoft 365 backup and restore service (distinct from Azure Backup) that provides point-in-time restore capabilities for Exchange Online mailboxes, SharePoint Online sites, and OneDrive accounts. It is managed entirely within the Microsoft 365 Admin Center and does not require Azure subscription or third-party backup tools.
💡 Microsoft 365 Backup vs Azure Backup — AB-650 Distinction
Microsoft 365 Backup (tested in AB-650 Domain 1) is the native M365 service accessed via the M365 Admin Center. It provides up to 1 year of backup retention and fast granular restore for M365 data. Azure Backup is a separate Azure service for VM disks, SQL databases, and on-premises servers. AB-650 tests Microsoft 365 Backup only — do not confuse the two.
Microsoft 365 Backup — Key Capabilities
| Workload | Backup Retention | Restore Granularity | Restore Time |
|---|---|---|---|
| Exchange Online mailboxes | Up to 180 days (6 months) | Full mailbox or individual items (emails, calendar, contacts) | Typically minutes to hours depending on mailbox size |
| SharePoint Online sites | Up to 180 days | Full site restore or granular item restore (files, lists, pages) | Typically minutes to hours depending on site size |
| OneDrive accounts | Up to 180 days | Full OneDrive restore or granular file/folder restore | Typically minutes to hours depending on data size |
Connect-MgGraph -Scopes "BackupRestore.Read.All","BackupRestore.ReadWrite.All" # Get the overall M365 Backup service status Get-MgSolutionBackupRestoreServiceApp | Select-Object Id,Status,LastModifiedDateTime | Format-List # Get Exchange Online protection policies (which mailboxes are protected) Get-MgSolutionBackupRestoreExchangeProtectionPolicy | Select-Object Id,DisplayName,Status,CreatedDateTime | Format-Table -AutoSize # Get SharePoint Online protection policies Get-MgSolutionBackupRestoreSharePointProtectionPolicy | Select-Object Id,DisplayName,Status,CreatedDateTime | Format-Table -AutoSize # Get OneDrive protection policies Get-MgSolutionBackupRestoreOneDriveForBusinessProtectionPolicy | Select-Object Id,DisplayName,Status,CreatedDateTime | Format-Table -AutoSize # List restore sessions (active or completed restores) Get-MgSolutionBackupRestoreRestoreSession | Select-Object Id,Status,CreatedDateTime,LastModifiedDateTime | Format-Table -AutoSize
🌐 Network Connectivity Insights
Network Connectivity Insights (Health → Network connectivity in the M365 Admin Center) provides visibility into how your organisation’s network is performing for Microsoft 365 traffic. It aggregates data from the Microsoft 365 connectivity test tool, the Windows 365 connectivity test, and optional on-premises data from the Network Connectivity Test scripts deployed to office locations.
Key Network Connectivity Metrics
| Metric | What It Measures | Threshold (Good) |
|---|---|---|
| Exchange Online latency | TCP connection latency from test location to Exchange Online front door | < 25ms |
| SharePoint Online download speed | File download speed from SharePoint Online CDN | > 1 Mbps |
| Microsoft Teams media quality | UDP packet loss, jitter, and latency for Teams media flows | < 1% loss, < 30ms jitter |
| DNS resolution time | Time to resolve Microsoft 365 service FQDNs | < 5ms |
| Office location mapping | Whether the test client’s egress IP is mapping to the nearest Microsoft network front door | Egress city matches office location |
💡 Why Network Connectivity Matters for AI Services
Microsoft 365 Copilot and Agent 365 are latency-sensitive workloads. Copilot responses involve real-time calls to Microsoft Graph, the Microsoft 365 semantic index, and LLM inference endpoints. Poor network connectivity (high latency, poor DNS resolution, suboptimal front door routing) directly degrades Copilot response times and user experience. An AB-650 administrator should review Network Connectivity Insights as part of the Copilot tenant readiness assessment in Module 7.
❤ Service Health Monitoring & Notifications
Service Health (Health → Service health in the M365 Admin Center) provides real-time status of all Microsoft 365 services and past incident history. For AB-650 administrators, service health monitoring includes the AI services: Microsoft 365 Copilot, Agent 365, and Copilot Studio now appear as separate monitored services.
Connect-MgGraph -Scopes "ServiceHealth.Read.All" # Get current service health status for all M365 services Get-MgServiceAnnouncementHealthOverview | Select-Object Service,Status | Sort-Object Service | Format-Table -AutoSize # Get only services with active issues Get-MgServiceAnnouncementHealthOverview | Where-Object {$_.Status -ne "ServiceOperational"} | Select-Object Service,Status | Format-Table -AutoSize # Get active incidents and advisories Get-MgServiceAnnouncementIssue -Filter "status ne 'resolved'" | Select-Object Id,Title,Service,Status,Classification,StartDateTime | Sort-Object StartDateTime -Descending | Format-Table -AutoSize # Get service health for Copilot and Agent 365 specifically Get-MgServiceAnnouncementHealthOverview | Where-Object {$_.Service -like "*Copilot*" -or $_.Service -like "*Agent*"} | Select-Object Service,Status | Format-Table -AutoSize # Get recent Message Center posts (new features and planned changes) Get-MgServiceAnnouncementMessage -Filter "lastModifiedDateTime gt 2026-01-01" | Select-Object Title,Category,Severity,LastModifiedDateTime | Sort-Object LastModifiedDateTime -Descending -First 10 | Format-Table -AutoSize
Service Health Email Notifications
Admins can configure email alerts so service incidents are sent automatically without requiring active monitoring of the admin center. Navigate to Health → Service health → Preferences → Email to configure:
- Email address(es) to receive service health alerts (up to 2 email addresses per admin)
- Which services to monitor (select all or specific services including Copilot, Agent 365)
- Alert frequency: Real-time alerts for new incidents, or a daily digest
- Major service incidents send immediate alerts regardless of frequency settings
🎓 Interview Q&A
An administrator needs to assign Microsoft 365 Copilot licences to 800 users in waves over the next quarter. Which approach ensures licences are automatically assigned when users join each rollout wave and automatically reclaimed when users are removed?
A user reports that they cannot access Microsoft Agent 365 features despite having Microsoft 365 Copilot assigned. The administrator checks the user’s licences and confirms only Microsoft 365 Copilot is assigned. What is the most likely resolution?
An organisation has configured Microsoft 365 Backup for Exchange Online mailboxes. A mailbox was accidentally deleted 45 days ago and needs to be restored. Which statement about the restore process is correct?
A newly added custom domain is showing a “Setup incomplete” status in Settings → Domains. The TXT verification record was added to the DNS registrar 2 hours ago. Users are reporting that email to the custom domain is not being delivered. What is the most likely cause?
An AB-650 administrator is preparing the tenant for a Microsoft 365 Copilot rollout. They want to identify office locations where users may experience slow Copilot response times due to network issues. Which M365 Admin Center section should they review?