Friday, May 1, 2026

SharePoint Online Administration & Architecture Complete Guide

SharePoint Online Administration & Architecture — Complete Guide

Site Hierarchy · Hub Sites · Information Architecture · Security · Administration · Content Management · Scenarios · Cheat Sheet

Core Concepts — Basics
Information Architecture & Hub Sites
Security, Permissions & Sharing
SharePoint Online Administration
Content Management & Key Features
Governance & Compliance
Scenario-Based Questions
Cheat Sheet — Quick Reference

1. Core Concepts — Basics

What is SharePoint Online and how does it fit in Microsoft 365?

SharePoint Online (SPO) is a cloud-based collaboration and content management platform included in Microsoft 365. It serves as the backbone for document management, intranet portals, team sites, and structured content.

SharePoint Online's role in Microsoft 365:

Document storage backbone: every Microsoft 365 Group, Teams channel, and OneDrive uses SharePoint Online as its underlying file storage
Intranet platform: communication sites, hub sites, and Viva Connections are built on SharePoint Online
Content services: Microsoft Syntex (content AI), Microsoft Purview (compliance), sensitivity labels all leverage SharePoint
Power Platform integration: Power Automate, Power Apps, and Power Pages connect to SharePoint lists and libraries

Key positioning: SharePoint Online is not just a file share — it is the content foundation of Microsoft 365.

What is the SharePoint Online site hierarchy?

Tenant (organisation)
  └── Site Collection (isolated container)
       ├── Root Site (top-level site)
       │    ├── Lists (structured data — rows & columns)
       │    ├── Libraries (document storage + metadata)
       │    ├── Pages (modern SharePoint pages)
       │    └── Web Parts (modular page components)
       └── Sub-sites (NOT recommended — use flat architecture instead)

Key components:
Site collection → isolated container: own permissions, storage quota, recycle bin
Site           → a website within a site collection
List           → structured data table (like a simple database)
Library        → document storage with metadata, versioning, check-out
Page           → modern web page built with web parts
Web Part       → modular content block (text, news, events, document library)

Warning: Sub-sites are a legacy pattern — avoid in modern SharePoint Online. Use separate site collections connected via Hub Sites instead. Sub-sites create complex permission inheritance issues.

What are the different types of SharePoint Online sites?

Site Type	Description	Best For
Team site	Connected to Microsoft 365 Group. Shared mailbox, calendar, Teams, Planner.	Team collaboration
Communication site	No M365 Group. Broadcasts information to wide audience.	Intranet portals, department sites
Hub site	A designation applied to an existing site. Connects associated sites.	Organisational grouping
Teams-connected	Every Teams channel has a corresponding SharePoint library.	File storage for Teams
OneDrive site	Each user's personal site collection.	Personal/private files

Tip: Communication site = publish TO many people. Team site = collaborate WITH a team. Hub site = connect related sites. These three distinctions are tested in every SharePoint .

What are SharePoint admin roles?

Role	Scope
Global Administrator	Full access to all SharePoint settings — too broad for daily use
SharePoint Administrator	Full SharePoint admin — all sites, settings, policies. Primary admin role.
Site Collection Administrator	Full control of a specific site collection
Site Owner	Manage a specific site — permissions, settings, pages
Site Member	Contribute — add, edit, delete content
Site Visitor	Read-only — view and download

Warning: Never use Global Administrator for routine SharePoint administration. Use the SharePoint Administrator role.

2. Information Architecture & Hub Sites

What is a Hub Site and what does it provide?

A Hub Site is an existing SharePoint site registered as a hub — connecting associated sites without creating a sub-site hierarchy.

What hub sites provide:

Unified navigation: hub nav bar displayed across all associated sites — changes propagate automatically
Shared branding: hub theme (colours, logo) applied consistently to all associated sites
Aggregated search: searching from any hub site or associated site searches the entire hub family
News rollup: News Web Part pulls news from all associated sites into the hub home page
People rollup: aggregate people across associated sites

Hub architecture example:
Contoso Intranet Hub (communication site — top-level hub)
  ├── HR Hub (communication site — sub-hub)
  │    ├── HR Policies (team site — associated to HR Hub)
  │    └── Benefits site (communication site — associated to HR Hub)
  ├── IT Hub (communication site — sub-hub)
  │    ├── IT Support site
  │    └── Infrastructure site
  └── Finance Hub
       ├── Finance team site
       └── Reporting site

Tip: Hub sites are the modern replacement for sub-sites. They provide organisational grouping benefits without the permission inheritance and governance problems.

What is the flat architecture principle in modern SharePoint?

Flat architecture: separate, independent site collections connected via Hub Sites — rather than a deep sub-site hierarchy.

Legacy (sub-site) architecture — AVOID:
/sites/contoso
  /sites/contoso/hr
    /sites/contoso/hr/policies
      /sites/contoso/hr/policies/2024

Problems:
→ Permissions cascade and are hard to manage
→ Sub-sites inherit parent permissions — hard to isolate
→ All sub-sites share root site storage quota
→ Cannot move sub-sites to different hub contexts

Modern (flat) architecture — RECOMMENDED:
/sites/intranet        ← Hub site
/sites/hr              ← Separate site collection (associated to Intranet hub)
/sites/hr-policies     ← Separate site collection (associated to HR sub-hub)
/sites/it              ← Separate site collection (associated to Intranet hub)

Benefits:
→ Each site has independent permissions
→ Each site has its own storage quota and recycle bin
→ Sites can be re-associated to different hubs as org evolves
→ Sites can be moved between hubs without restructuring

What are Managed Metadata and Content Types?

Managed Metadata (Term Store): centrally managed taxonomy of terms applied as metadata columns across all sites in the tenant. Enables consistent tagging and filtering.

Content Types: reusable definitions for a type of document or list item — specifying columns, document template, workflows, and retention policies. Defined once in the Content Type Hub and published to all sites.

Example:
Term Store: Department
  Terms: HR / Finance / IT / Legal / Operations

Content Type: "Contract Document"
  Columns: Title, Department (managed metadata), Effective Date,
           Expiry Date, Contract Value, Counterparty
  Template: Contract_Template.docx
  Retention: 7 years after expiry date

When a user creates a "Contract Document" in ANY library:
→ Pre-configured template automatically applied
→ Required metadata fields enforced
→ Document follows 7-year retention policy automatically
→ Consistent across ALL sites and ALL libraries in the tenant

Tip: Content Types + Managed Metadata is the foundation of enterprise information architecture in SharePoint. Any question about governance, compliance, or findability leads to this answer.

What are the SharePoint URL patterns and character limits?

SharePoint Online URL patterns:
Tenant root:       https://contoso.sharepoint.com
Team sites:        https://contoso.sharepoint.com/sites/{sitename}
Communication:     https://contoso.sharepoint.com/sites/{sitename}
OneDrive:          https://contoso-my.sharepoint.com/personal/{username_contoso_com}
Admin Centre:      https://contoso-admin.sharepoint.com

Important limits:
Maximum URL length:         400 characters (file path + filename)
Maximum filename length:    256 characters
Maximum file size:          250 GB per file
Maximum list items:         30 million items per list (with index)
Maximum library items:      No hard limit (but performance degrades > 5,000 without indexing)
List view threshold:        5,000 items per view (requires indexed columns to exceed)
Maximum site storage:       25 TB per site (or tenant pool limit)

3. Security, Permissions & Sharing

What are SharePoint permission levels?

Built-in permission levels (most → least permissive):
Full Control   → complete access — manage, configure, delete the site
Design         → create lists/libraries, edit pages, apply themes
Edit           → add, edit, delete items AND manage lists
Contribute     → add, edit, delete items (cannot manage lists)
Read           → view items, open/download documents
View Only      → view in browser only (cannot download — for DRM)
Limited Access → system-generated — access to specific items only

Assigned via SharePoint Groups:
Site Owners   → Full Control (default)
Site Members  → Edit (modern) or Contribute (classic)
Site Visitors → Read (default)

Three-layer model:
Users → SharePoint Groups → Permission Levels → Site/List/Library

Tip: Permission levels are templates. Groups hold users. Groups are assigned permission levels. This three-layer model is tested in every SharePoint security .

What is permission inheritance and when should you break it?

By default, lists, libraries, folders, and items inherit permissions from their parent site.

When to break inheritance — legitimate:

A library contains confidential HR files on a general site → break library inheritance, add HR team only
A specific document needs to be shared with external users → share the item directly

When NOT to break inheritance:

Breaking inheritance on dozens of folders in a library → creates unmanageable permission matrix
Breaking inheritance instead of creating a separate site → if access requirements differ significantly, create a new site

Best practices:
→ Manage permissions at SITE level (not list/library/item where possible)
→ Use separate sites for content with different access requirements
→ Item-level sharing is acceptable for exceptions, not systematic use
→ Audit broken inheritance regularly: Get-PnPList | Where-Object HasUniqueRoleAssignments

Critical: Over-breaking inheritance is the #1 SharePoint governance anti-pattern. It creates "permission hell" where nobody can determine who has access to what.

What are sharing settings in SharePoint Online?

External sharing controls who can share content with people outside the organisation.

Policy	Description	Risk Level
Anyone (anonymous links)	Share with anyone — no login required	High
New and existing guests	External users must authenticate (Entra B2B or OTP)	Medium
Existing guests only	Only users already in the Azure AD guest directory	Low
Only people in your org	No external sharing at all	None

Governance controls:
→ Set tenant policy restrictively → override per site as needed
→ Site policy can only be EQUAL TO or MORE RESTRICTIVE than tenant
→ Set link expiry dates on anonymous links (e.g., 30 days)
→ Require re-authentication after X days for guest users
→ Restrict sharing to specific domains (allow/block list)
→ Require approval for external sharing via access requests

What are Sensitivity Labels in SharePoint Online?

Sensitivity Labels (Microsoft Purview) applied to SharePoint sites enforce data protection policies at the container level.

Sensitivity label capabilities on sites:
Privacy setting:          Enforce site privacy (Public/Private)
External sharing:         Block external sharing (e.g., "Highly Confidential" = no external)
Unmanaged device access:  Browser-only on personal devices, no download
Teams/Groups settings:    Control guest access, meeting options

Example:
Owner creates site → selects "Highly Confidential" label
Label automatically:
→ Sets privacy = Private (cannot be changed by owner)
→ Disables external sharing for this site
→ Restricts personal device access to browser-only
→ Applies to all documents in the site (auto-labelling)
→ Reports to Purview compliance portal for audit

4. SharePoint Online Administration

What is the SharePoint Admin Centre?

The SharePoint Admin Centre (admin.microsoft.com → SharePoint) is the central management portal.

Section	Capabilities
Sites	View all sites, create/delete, storage quotas, set admins, configure sharing per site
Policies	Sharing settings, access control, device policies, idle session sign-out
Settings	Storage limits, site creation settings, OneDrive settings
Content services	Term Store, Content Type Gallery, Microsoft Syntex
Migration	Migration Manager for file server/Google Drive to SharePoint
Reports	Active sites, storage usage, sharing activity

What is SharePoint PowerShell — PnP PowerShell vs SPO Management Shell?

SPO Management Shell (Microsoft.Online.SharePoint.PowerShell): Microsoft's official module for tenant-level administration.

PnP PowerShell (PnP.PowerShell): community-driven module with 500+ cmdlets covering tenant administration AND site-level content management, provisioning, and automation.

# SPO Management Shell — tenant admin:
Connect-SPOService -Url https://contoso-admin.sharepoint.com
Get-SPOSite -Limit ALL | Where-Object {$_.StorageUsageCurrent -gt 1000}
Set-SPOSite -Identity https://contoso.sharepoint.com/sites/hr -StorageQuota 5120
Set-SPOTenant -SharingCapability ExternalUserSharingOnly
New-SPOSite -Url https://contoso.sharepoint.com/sites/newsite -Owner admin@contoso.com -StorageQuota 1024

# PnP PowerShell — site content and config:
Connect-PnPOnline -Url https://contoso.sharepoint.com/sites/hr -Interactive
Get-PnPList | Select-Object Title, ItemCount
Add-PnPField -List "Documents" -DisplayName "Department" -InternalName "Dept" -Type Choice
Apply-PnPProvisioningTemplate -Path ./site-template.xml
Get-PnPSiteTemplate -Out ./site-backup.xml

Tip: PnP PowerShell is the go-to tool for most SharePoint automation. SPO Management Shell for tenant-level operations PnP doesn't cover (CDN configuration, tenant sharing settings).

What is SharePoint storage management?

SharePoint Online storage model:
Tenant storage pool:
  1 TB base + 10 GB per licence purchased
  Example: 500 users → 1 TB + 5 TB = 6 TB total pool

Site storage:
→ Each site draws from the tenant pool
→ Default: each site gets up to 25 TB (or pool limit)
→ Admins set per-site storage quotas (in MB) in Admin Centre

OneDrive storage (separate from SharePoint pool):
→ Each user: 1 TB (or more with licence)

Storage consumers to monitor:
→ Version history: each version = complete file copy
   100 versions × 10 MB = 1 GB per document
→ Recycle bins: first + second stage count against quota
→ Large file libraries without version limits → storage bloat

Remediation:
→ Set version limits (major only, limit to 50)
→ Schedule recycle bin emptying
→ Run storage reports: SharePoint Admin Centre → Sites → Storage Used
→ PnP: Get-PnPSite -Includes StorageUsage, StorageMaximumLevel

What is the Site Lifecycle and how do you manage it?

Site lifecycle stages:
1. Provisioning  → controlled creation (self-service or admin-approved)
2. Active use    → regular access tracked via usage analytics
3. Inactive      → no activity for 180 days → Microsoft notifies owner
4. Review        → owner confirms: still needed or ready for deletion
5. Archival      → content archived before deletion if needed
6. Deletion      → soft delete → 93-day recovery window
7. Permanent delete → after 93 days, irrecoverable

Key facts:
→ 93-day recovery window for deleted sites in Admin Centre recycle bin
→ After 93 days: permanently deleted — no recovery
→ Microsoft 365 inactive site policies: auto-detect and notify
→ Always confirm with site owner before deleting — inactive ≠ dead

Tip: The 93-day recovery window is a critical fact in every SharePoint admin . After this period, all content is permanently gone. Always verify with owners before deletion.

5. Content Management & Key Features

What is versioning in SharePoint Online?

Version types:
Major only:           1.0, 2.0, 3.0 — published versions
Major + minor:        1.0, 1.1, 1.2, 2.0 — drafts (minor) + published (major)

Storage impact:
Each version = complete file copy
100 versions × 10 MB document = ~1 GB storage consumed
Unlimited versioning → storage bloat on large libraries

Recommended configuration:
Document libraries:  Major versions only, limit to 50
Intranet pages:      Major + minor, limit 10 major + 10 minor
Compliance:          Major + minor, no limit (regulatory requirement)

Restore previous version:
Via UI: Document → Version History → Restore
Via PnP: Restore-PnPFileVersion -Url /sites/hr/docs/policy.docx -Identity 3.0

What are SharePoint Lists vs Libraries?

SharePoint List: structured data storage — rows and columns. Stores data (not files).

SharePoint Library: document storage with metadata — each row is a file with associated metadata columns. Adds versioning, check-in/out, and co-authoring.

	List	Library
Stores	Data (items/rows)	Files (documents)
Versioning	Yes (optional)	Yes (recommended)
Check-in/out	No	Yes
Templates	No	Yes (per content type)
Use for	Issue trackers, tasks, asset registers, contacts	Policies, contracts, reports, templates

What is the SharePoint List View Threshold (LVT)?

List View Threshold: 5,000 items per view
→ SharePoint throttles queries returning > 5,000 items in a single view
→ Returns error: "This view cannot be displayed because it exceeds the list view threshold"

Workarounds:
1. Create indexed columns on the most-filtered columns
   → Index: Status, Department, Created, Modified
2. Use filtered views that return < 5,000 items
3. Use modern search instead of list views for large lists
4. Use Power BI or Power Apps for large data visualisation
5. Archive old items to a separate "Archive" library periodically

Indexing:
→ List Settings → Indexed columns → add up to 20 indexes
→ Always index columns used in view filters, sorts, and group-by
→ Required BEFORE the list grows beyond 5,000 items
   (cannot add index to column if list already > 5,000 and no index exists)

Warning: Adding indexes to large lists (>5,000 items) when no index exists can fail. Always add indexes proactively when creating lists that may grow large.

What is Microsoft Syntex?

Microsoft Syntex is a content AI service automatically extracting, classifying, and processing content in SharePoint libraries.

Feature	Description
Document understanding	Train AI models to classify documents and extract fields (invoice → vendor, amount, date)
Form processing	Extract structured data from forms and PDFs
Auto-tagging	Automatically apply content types and metadata to uploaded documents
Content assembly	Generate documents from templates using SharePoint data
eSignature	Send documents for e-signature directly from SharePoint
Microsoft 365 Backup	Rapid point-in-time restore of sites, libraries, or items

Tip: Syntex solves the "metadata entry burden" problem — the main reason SharePoint metadata strategies fail in practice. Auto-classification means users don't have to manually tag every uploaded document.

What is SharePoint Search and how does it work?

SharePoint Online search key concepts:
Crawl          → automatic continuous crawling (no manual schedule needed)
Managed props  → searchable/queryable metadata (Author, Created, ContentType)
Security trim  → users only see results they have permission to access (always on)
Query rules    → promote specific results for specific queries
Result sources → scope search to specific locations (site, library, content type)

Microsoft Search (modern):
→ AI-powered, graph-aware, works in SharePoint, Teams, Office apps
→ Bookmarks: admin-configured top results ("IT Helpdesk" always returns IT support site)
→ Acronyms, Q&A, Floor plans: additional answer types

Classic search (legacy):
→ Customisable result pages, query rules, promoted results
→ Being phased out — use Microsoft Search for new implementations

Configure Microsoft Search answers:
Microsoft 365 Admin Centre → Search & Intelligence → Answers
→ Bookmarks: pin specific URLs for specific search queries
→ Q&A: define answers to common questions
→ Acronyms: define org-specific abbreviations

6. Governance & Compliance

What are the key SharePoint governance controls?

Control	Description
Site creation policy	Restrict self-service site creation to specific groups or admins only
External sharing policy	Tenant + per-site sharing levels, domain restrictions, link expiry
Sensitivity labels	Enforce data protection at container level
Retention policies (Purview)	Retain or delete content based on age or label
DLP policies	Detect and block sharing of sensitive content (SSN, credit card, etc.)
Conditional Access	Restrict access from unmanaged devices, specific IPs, or locations
Information barriers	Prevent certain groups from communicating or sharing with each other
eDiscovery & Legal holds	Preserve content for legal proceedings

What is Microsoft Purview integration with SharePoint Online?

Purview capabilities for SharePoint:
Retention policies:
→ Retain content for X years (cannot be deleted during retention)
→ Delete content after X years (auto-disposal)
→ Apply to: all SPO sites, specific sites, or by sensitivity label
→ Disposition review: human review required before permanent deletion

DLP policies:
→ Detect sensitive data in SharePoint (credit card numbers, NHS numbers, etc.)
→ Actions: block sharing externally, alert admin, notify user
→ Works on files AND list items

eDiscovery:
→ Search across SharePoint and other M365 services for legal matters
→ Place content on Legal Hold — prevents deletion even if retention period ends
→ Export content in standard formats for legal review

Audit log:
→ All SharePoint activity logged (file access, permission changes, sharing)
→ Retention: 90 days (standard) / 1 year (M365 E3) / 10 years (E5 compliance)
→ Search via: Purview compliance portal → Audit

What is Conditional Access for SharePoint Online?

Conditional Access policies (configured in Entra ID / Azure AD) can restrict SharePoint access based on device compliance, location, or risk level.

SharePoint-specific Conditional Access scenarios:
Unmanaged devices:
→ Allow full access from Intune-managed devices
→ Browser-only (no download, no sync) from personal/unmanaged devices
→ Block access entirely from non-compliant devices

Network location:
→ Only allow access from corporate IP ranges
→ Block access from specific countries

Sensitivity label integration:
→ "Highly Confidential" label automatically enforces browser-only on unmanaged devices
→ No separate Conditional Access policy needed — label handles it

Configure in SharePoint Admin Centre → Policies → Access control
→ Unmanaged devices: Allow full access / Limited browser-only / Block
→ Network location: specify allowed IP ranges

7. Scenario-Based Questions

Scenario: Design a SharePoint Online intranet for a 5,000-person organisation with 10 departments.

Architecture:

Root/Intranet Hub: communication site registered as top-level hub. Contains: global news, CEO announcements, company-wide navigation, Viva Connections integration.
Departmental sub-hubs (×10): each department gets a communication site registered as a hub associated to the Intranet Hub:
- HR Hub, IT Hub, Finance Hub, Marketing Hub, Legal Hub, etc.
Team collaboration sites: each team/project gets a Team site associated to its departmental hub. Microsoft 365 Group-connected → automatic Teams, mailbox, Planner.
Information architecture:
- Term Store: Department, Location, Topic, Document Type
- Content Types: Policy, Procedure, Report, Contract — published from Content Type Hub
- Required metadata on all library content types
Navigation: Hub navigation per hub level. Global navigation via Viva Connections app bar.
Search: Microsoft Search Bookmarks for key destinations (HR portal, IT helpdesk, Finance reporting). Verticals for People, Departments, Policies.
Governance: PnP provisioning templates for consistent site creation. Sensitivity labels for confidential sites. External sharing: blocked by default, enabled per-site on request with approval workflow.

Scenario: Users are accidentally deleting documents. How do you prevent and recover?

Prevention:

Custom permission level "Contribute without Delete": remove the "Delete Items" permission. Assign to regular users — they can edit but not delete.
Require check-out on critical libraries: users must check out before editing — prevents accidental overwrites.
Retention policy (Purview): during retention period, even site owners cannot permanently delete content.
Versioning: ensure versioning is enabled — overwritten documents have recoverable previous versions.

Recovery:

Site recycle bin: available for 93 days. Site owners can restore.
Second-stage recycle bin: site collection admin recycle bin — another 93-day window after first-stage deletion.
Microsoft 365 Backup (Syntex): rapid point-in-time restore of libraries or entire sites.

# Restore from recycle bin via PnP:
Restore-PnPRecycleBinItem -Identity $itemGuid

# Check recycle bin contents:
Get-PnPRecycleBinItem | Sort-Object DeletedDate -Descending | Select-Object -First 20

Scenario: How do you migrate 10TB of file server content to SharePoint Online?

Assessment: SharePoint Migration Assessment Tool (SMAT) — scan file server for file count, total size, path length issues (max 400 chars), special characters, blocked file types.
Information architecture design: map folder structure to SharePoint sites/libraries. Avoid replicating deep folders — redesign with metadata. "2024" folder → Year metadata column.
Target provisioning: create destination sites and libraries using PnP PowerShell provisioning templates.
Migration Manager (SharePoint Admin Centre):
- Install agent on file server
- Set up migration tasks: source folder → destination library
- Run pre-migration scan for errors

Phased migration:

Phase 1: Pre-migration copy (overnight — bulk of data)
Phase 2: Delta copy (capture changes since pre-migration)
Phase 3: Cutover (set source to read-only, final delta, redirect users)

Permission mapping: Migration Manager maps file server ACLs to SharePoint groups. Validate and simplify — fewer, broader permissions are easier to maintain.
User communication: training on new SharePoint experience, new URL bookmarks, OneDrive sync client configuration.

Tip: Migration is the opportunity to redesign with flat structure + metadata. Never replicate the folder hierarchy as-is.

Scenario: Implement a document management system in SharePoint for a legal team.

Dedicated site: Legal team site, restricted access. Sensitivity label "Confidential" → enforces Private, no external sharing, browser-only on unmanaged devices.
Content types: "Contract", "Legal Opinion", "Court Filing", "NDA" — each with metadata columns (Matter number, Client, Jurisdiction, Counterparty, Effective Date, Expiry Date).
Managed metadata: Term Store for Jurisdiction (UK, EU, US, APAC) and Practice Area (Corporate, Litigation, Employment, IP).
Versioning: Major + minor versions, no version limit — full audit trail required for legal compliance.
Retention policies (Purview): 7-year retention on all contract documents. Disposition review workflow at end of retention period before permanent deletion.
Access control: matter-level permissions — only lawyers on a specific matter access that matter's documents. Break inheritance at folder/library level per matter.
Microsoft Syntex: auto-classify uploaded documents by type, extract key metadata (counterparty, dates, values) automatically.
eDiscovery: Microsoft Purview eDiscovery integration — legal holds on relevant content, search across all legal documents for litigation support.

Scenario: How do you handle a site that has grown to 500,000+ documents with slow search and list view errors?

List View Threshold: ensure indexed columns are configured on all columns used in view filters, sort, and group-by. Views must filter to < 5,000 items.
```
Add-PnPIndex -List "Documents" -Field "Department"
Add-PnPIndex -List "Documents" -Field "Year"
```
Archive old content: move documents older than X years to an archive library or separate "Archive" site — reduces active library size.
Metadata-based navigation: replace folder-based navigation with metadata navigation (filtered views by Year, Department, Content Type).
Search instead of views: for ad-hoc queries across 500K documents, direct users to Microsoft Search rather than list views.
Microsoft Syntex: if documents are untagged, use Syntex auto-classification to bulk-apply metadata — enables proper filtered views.
Power BI report: for data analysis across large libraries, connect Power BI to SharePoint list API — handles large item counts better than list views.

8. Cheat Sheet — Quick Reference

Site Types Quick Reference

Communication site:
→ No M365 Group
→ Publish TO a wide audience
→ Intranet portals, department sites, news sites
→ Hub site candidate

Team site:
→ Connected to M365 Group
→ Collaborate WITH a team
→ Shared mailbox, calendar, Teams, Planner auto-created
→ Associate to a hub for organisational grouping

Hub site:
→ An existing site registered as a hub
→ Provides: unified nav, shared theme, aggregated search + news
→ Up to 2,000 associated sites per hub
→ Up to 26 hub-to-hub associations

OneDrive:
→ Personal site collection per user
→ Private files + sync to local device
→ 1 TB per user (more with enterprise licence)

SharePoint Permissions Model

Users → SharePoint Groups → Permission Levels → Content

Default groups:
Site Owners   → Full Control
Site Members  → Edit (modern) / Contribute (classic)
Site Visitors → Read

Custom permission level example — "Contribute without Delete":
Clone Contribute → uncheck "Delete Items" → Save as new level
Apply to a new group → add users who should contribute but not delete

Permission inheritance:
By default: list/library/item inherits from parent site
Break inheritance: creates unique permissions for that object
Avoid over-breaking inheritance — creates unmanageable complexity

External Sharing Quick Reference

Tenant sharing levels (most → least permissive):
1. Anyone (anonymous links — highest risk)
2. New and existing guests (Entra B2B or OTP auth required)
3. Existing guests only (must already be in Azure AD)
4. Only people in your organisation (no external sharing)

Site-level can only be equal to or more restrictive than tenant level

Governance checklist:
☐ Set tenant to "New and existing guests" or stricter
☐ Set anonymous link expiry (30 days max recommended)
☐ Restrict to allowed domains list for specific sites
☐ Enable access request approval workflow
☐ Block sharing from sensitive sites with sensitivity labels
☐ Review guest access quarterly via Entra ID Access Reviews

Storage Management Quick Reference

Tenant storage: 1 TB + 10 GB per licence
Per-site quota: set in Admin Centre (MB)
OneDrive: separate from SharePoint pool

Storage consumers:
Version history → set major only, limit to 50 versions
Recycle bins   → first + second stage count against quota
Large files    → identify and archive via PnP

PowerShell commands:
# Get all sites by storage:
Get-SPOSite -Limit ALL | Sort-Object StorageUsageCurrent -Descending

# Set site quota (100 GB = 102400 MB):
Set-SPOSite -Identity $siteUrl -StorageQuota 102400

# Get library storage breakdown (PnP):
Get-PnPFolderStorageMetric -FolderSiteRelativeUrl "Shared Documents"

Key Limits Reference

URL path:          400 characters max
Filename:          256 characters max
File size:         250 GB per file max
List items:        30 million max (with index)
LVT:               5,000 items per view (without index)
Indexed columns:   20 per list
Site storage:      25 TB per site
Recycle bin:       93 days recovery window
Anonymous links:   Up to 30 days (recommended)
Hub associations:  2,000 sites per hub
Hubs per tenant:   2,000

Top 10 Tips

Communication vs Team vs Hub — the three-way distinction is tested in every SharePoint . Communication = broadcast. Team = collaborate. Hub = connect. Never confuse them.
Flat architecture over sub-sites — modern SharePoint is flat (separate site collections connected by hubs). Sub-sites are legacy and create governance problems. Proactively recommend flat architecture.
Content Types + Managed Metadata — the foundation of enterprise information architecture. Any question about governance, compliance, or findability leads here.
Permission levels → Groups → Users — the three-layer model. Never add individual users directly to content — always use groups.
Break inheritance sparingly — item/folder-level permission breaks are the #1 governance anti-pattern. Use separate sites for different access requirements instead.
Site-level sharing can only be more restrictive than tenant — tenant sets the ceiling. Sites can tighten further but never exceed the tenant policy.
93-day recycle bin window — after this, deleted sites and content are permanently gone. Always confirm with owners before deletion.
List View Threshold = 5,000 — without indexes, views fail beyond 5,000 items. Add indexes proactively on filter/sort columns before the list grows. Cannot add index after exceeding LVT without an existing index.
PnP PowerShell for automation — know the key PnP cmdlets: Connect-PnPOnline, Get-PnPList, Apply-PnPProvisioningTemplate, Get-PnPSiteTemplate. These come up in every technical round.
Microsoft Syntex solves metadata adoption — the real reason SharePoint metadata fails is user adoption. Syntex auto-tags and auto-classifies — removing the manual burden. This is the modern governance answer.

Dynamics 365 Sales & CRM Complete Guide

Dynamics 365 Sales & CRM — Complete Guide

Lead Management · Sales Pipeline · Quotes & Orders · AI Copilot · Forecasting · Scenarios · Cheat Sheet

Core Concepts — Basics
Sales Pipeline & Opportunity Management
Products, Quotes & Orders
AI Features & Copilot for Sales
Sales Accelerator & Sequences
Forecasting & Goals
Configuration, Security & Integration
Scenario-Based Questions
Cheat Sheet — Quick Reference

1. Core Concepts — Basics

What is Dynamics 365 Sales and what are its core capabilities?

Dynamics 365 Sales is a cloud-based CRM application built on Dataverse that helps sales organisations manage their entire sales process — from lead generation to deal closure.

Core capabilities:

Lead management: capture, qualify, and convert leads into opportunities
Opportunity management: track deals through a defined sales pipeline with stages
Account & Contact management: 360-degree view of customers and key contacts
Activity management: emails, calls, meetings, tasks linked to sales records
Quote-to-Order: create quotes, orders, and invoices within the CRM
Sales forecasting: predict revenue based on pipeline and deal probabilities
AI & Copilot: relationship intelligence, conversation intelligence, predictive scoring
Sales analytics: dashboards and reports on pipeline health, win rates, team performance

What are the main tables (entities) in D365 Sales?

Core Sales entity relationships:

Lead → (qualify) → Contact + Account + Opportunity
                                          ↓
                                       Quote(s)
                                          ↓
                                       Order(s)
                                          ↓
                                       Invoice(s)

Key entities:
Lead         → unqualified prospect. Not yet a customer in the system.
Contact      → individual person. Related to Account.
Account      → company/organisation. Parent of Contacts.
Opportunity  → potential deal. Linked to Account + Contact.
Quote        → formal price proposal. Created from Opportunity.
Order        → confirmed purchase. Created from Quote.
Invoice      → billing document. Created from Order.
Product      → item sold. Added to Quote/Order as line items.
Price List   → defines pricing for products per market/currency.
Competitor   → tracks competing vendors in a deal.
Goal         → revenue/activity target for a rep or team.
Territory    → geographic or account-based sales assignment.

Tip: The Lead → Opportunity → Quote → Order → Invoice pipeline is the most tested D365 Sales sequence in. Know every step and what triggers each conversion.

What are the D365 Sales licensing tiers?

Licence	Key Features
Sales Professional	Core CRM — leads, opps, accounts, contacts, activities, basic dashboards
Sales Enterprise	All Professional + sequences, forecasting, relationship analytics, conversation intelligence, LinkedIn integration
Sales Premium	All Enterprise + predictive lead/opportunity scoring, advanced AI relationship analytics
Microsoft Relationship Sales (MRS)	Sales Enterprise + LinkedIn Sales Navigator — combined licence
Copilot for Sales	AI assistant across Outlook, Teams, D365 — meeting summaries, email drafting, CRM updates

What is the difference between a Lead and an Opportunity?

Lead: an unqualified potential prospect. Represents an expression of interest not yet evaluated. May be a real buyer or may be disqualified. Stored in a separate Lead table — NOT yet an Account/Contact in the system.

Opportunity: a qualified, viable potential deal. Has confirmed buying intent, budget, and authority. Linked to an existing Account and Contact. Has an estimated value, close date, and sales stage.

Lead qualification decision:
"Is this a real sales opportunity?"

YES → Qualify lead → system creates:
  → Contact (the person)
  → Account (the company)
  → Opportunity (the deal)
  All linked and pre-populated from lead data

NO → Disqualify lead:
  Status reasons: Lost / No Longer Interested / Cannot Contact

Key distinction:
Lead = potential interest, no confirmed customer record
Opportunity = confirmed prospect with Account and Contact in the system

Tip: Never create an Opportunity directly without a Lead (unless the Account already exists). Lead qualification is the data quality gate — it prevents polluting the system with unqualified prospects as Accounts.

What activities are used in D365 Sales and how are they tracked?

Activity	Description
Email	Sent/received emails tracked from Outlook via D365 App for Outlook
Phone Call	Outbound/inbound calls logged manually or via Conversation Intelligence
Appointment	Meetings linked to D365 records — syncs with Outlook Calendar
Task	Follow-up actions assigned to reps with due dates
Teams call	Recorded via Conversation Intelligence

All activities are linked to a Regarding record (Lead, Opportunity, Account, Contact) and appear in the unified timeline on that record's form.

2. Sales Pipeline & Opportunity Management

What is a Business Process Flow (BPF) for Opportunities?

A Business Process Flow is a stage-based visual guide overlaid on the Opportunity form — ensuring consistent sales methodology across all reps.

Default Opportunity Sales Process stages:
1. Qualify   → confirm BANT (Budget, Authority, Need, Timeline)
   Required steps: Est. Revenue, Decision Maker?, Identify Sales Team
2. Develop   → understand requirements, solution mapping
   Required steps: Customer Need, Proposed Solution, Identify Competitors
3. Propose   → formal proposal / quote presentation
   Required steps: Identify Key Stakeholders, Present Proposal
4. Close     → negotiate and get final decision
   Required steps: Complete Final Proposal, Confirm Decision Date, Final Proposal Sent

Custom BPF example (MEDDIC methodology):
Metrics → Economic Buyer → Decision Criteria → Decision Process → Identify Pain → Champion

BPF data stored in Dataverse:
→ Active stage, days in each stage, stage completion %
→ Reportable in Power BI for funnel/conversion analysis

Tip: BPF stage data is stored in Dataverse and fully reportable. "Days in stage" and "stage-to-stage conversion rate" are critical pipeline health metrics available only because of the BPF.

What are Opportunity Close reasons and why are they important?

Close as Won dialog:
→ Actual Revenue: confirmed deal value (may differ from estimated)
→ Actual Close Date: when deal was signed
→ Competitor: who else was considered
→ Description: close notes

Close as Lost dialog:
→ Status Reason (REQUIRED custom field — make it mandatory):
   Lost to Competitor / No Budget / No Decision Made /
   Product Not a Fit / Wrong Timing / Relationship Lost
→ Competitor: who won the deal
→ Description: detailed loss notes

Why loss reasons matter:
→ Win/loss by competitor: identify which competitors you lose to most → competitive battlecards
→ Win/loss by product: identify product gaps → roadmap input
→ Win/loss by rep: identify coaching needs → training
→ Win/loss by stage: identify where deals fall off → process improvement
→ Win/loss by deal size: identify sweet spot → ICP refinement

Tip: Always make loss reason a required field on the Close as Lost dialog. Without required loss reasons, reps enter generic answers and the data becomes useless for analysis.

What is the Opportunity probability and how is it used?

Opportunity Probability (0–100%) indicates the likelihood of winning the deal. In the default setup it is manually set by the rep, often tied to the sales stage:

Default probability by stage:
Qualify:  10%
Develop:  20%
Propose:  50%
Close:    75%
Won:     100%
Lost:      0%

Used in forecasting calculations:
Expected Revenue = Estimated Value × Probability
($500,000 × 75%) = $375,000 expected revenue

With Predictive Opportunity Scoring (Sales Premium):
→ AI calculates probability based on historical win patterns
→ Overrides manual probability with data-driven score
→ Factors: deal age, activity level, stakeholder engagement, competitive presence

3. Products, Quotes & Orders

What is the Product Catalog in D365 Sales?

Component	Description
Product families	Hierarchical grouping. Shared properties inherited by child products.
Products	Individual items or services with default price and unit.
Unit groups	Units of measure (e.g., "Pieces": Each, Dozen, Pack) with conversion factors.
Price lists	Selling prices per market, currency, customer segment, or promotion.
Price list items	Link product to price list with specific price (fixed or % of list).
Discount lists	Volume-based or criteria-based discounts applied to quote lines.

Example product catalog:
Product Family: Software Licences
  Product: CRM Starter (annual)    → $1,200/seat
  Product: CRM Enterprise (annual) → $2,400/seat
  Product: CRM Premium (annual)    → $3,600/seat

Price Lists:
  EMEA GBP List: CRM Starter £950, Enterprise £1,900
  APAC USD List: CRM Starter $1,100, Enterprise $2,200
  Partner List:  20% discount off standard list price

Unit Groups:
  Software: Seat / 5-Pack (4.5×/seat) / 25-Pack (4×/seat)

What is the Quote lifecycle in D365 Sales?

Quote statuses:
Draft    → being built. Fully editable. Not sent to customer.
Active   → locked and sent to customer. Cannot be edited directly.
Won      → customer accepted. Triggers Order creation.
Closed   → declined or expired.
Revised  → new Draft version created from an Active quote.

Lifecycle flow:
[Draft] → Add products, pricing, discounts, terms
       → [Activate] → Quote locked, PDF generated, sent to customer
       → Customer responds:
            Accepted  → [Won] → Create Order from Quote
            Declined  → [Closed]
            Needs changes → [Revise] → New Draft created
                             Previous Active quote auto-closed

Quote line items:
→ Catalog products with quantity, unit, price, discount, tax
→ Write-in products: non-catalog items (custom services)
→ Manual price override (with approval workflow if configured)
→ Sub-totals, pre-freight total, freight, discount, tax, total amount

Warning: Once a Quote is Activated it is locked for editing. Use "Revise" to make changes — this creates a new Draft and closes the previous Active quote. Maintain revision history for audit purposes.

What are the key differences between Quote, Order, and Invoice?

	Quote	Order	Invoice
Represents	Price proposal	Confirmed purchase	Billing document
Created from	Opportunity	Won Quote (or directly)	Order
Customer committed	No	Yes	Yes
Editable	Yes (Draft) / No (Active)	Yes (Active)	Limited
Key statuses	Draft → Active → Won/Closed	Active → Fulfilled → Cancelled	Active → Paid → Cancelled
Triggers	—	Fulfilment / delivery process	Payment processing

D365 Sales vs ERP:
D365 Sales: Quote/Order/Invoice for CRM pipeline visibility
ERP (Business Central, SAP): Full financial processing
  → GL posting, inventory management, payment reconciliation
  → Integration: D365 Order → ERP Order → ERP Invoice → D365 Invoice sync

4. AI Features & Copilot for Sales

What is Copilot for Sales and what can it do?

Copilot for Sales (formerly Viva Sales) is an AI assistant working across Microsoft 365 and D365 Sales.

Capability	Description
Email summary & response	Summarises email threads, drafts contextually relevant replies with CRM data
Meeting preparation brief	Before a Teams meeting: account info, open opps, recent activities, talking points
Meeting summary & actions	After Teams meeting: summary, action items, suggested CRM updates
CRM updates from Outlook/Teams	Update opp stage, close date, notes without switching to D365
Opportunity summary	One-click AI summary: key details, recent activities, stakeholders, risks

Tip: Copilot for Sales is the answer to "how do you increase CRM adoption." Reps work in Outlook and Teams — Copilot brings CRM into their daily workflow rather than requiring a context switch to D365.

What is Predictive Lead and Opportunity Scoring?

Both use ML models trained on historical D365 data to assign a score (0–100) and grade (A/B/C/D).

Predictive Lead Scoring (Sales Premium):
Analyses: firmographics, lead source, engagement signals, demographics
Score: 0-100 (A=80-100, B=60-79, C=40-59, D=0-39)
Shows: influencing factors (positive/negative)
Use: prioritise high-grade leads in the Sales Accelerator worklist

Predictive Opportunity Scoring (Sales Premium):
Analyses: deal age, activities, stakeholder engagement, competitor presence,
          product mix, historical win patterns
Score: 0-100
Shows: factors driving score up or down
Use: identify at-risk opportunities, prioritise rep focus

Model training:
→ Trained on YOUR org's historical Won/Lost opportunities
→ Requires ~40+ won + 40+ lost opportunities to activate
→ Auto-refreshes weekly as new data accumulates
→ Gets more accurate over time — self-improving

Key point: The model is trained on YOUR organisation's data — not generic industry benchmarks. It improves as you close more deals. Mention this to show deep understanding.

What is Conversation Intelligence?

Conversation Intelligence analyses recorded Teams sales calls using AI to extract insights and coaching opportunities.

Call recording and transcription: auto-records Teams calls, transcribes speech to text
AI analysis: extracts keywords, topics, competitor mentions, action items, customer questions
Talk-to-listen ratio: measures rep vs customer speaking time — coaching signal (ideal: rep speaks <50% of the time)
Keyword tracking: alerts when tracked keywords mentioned (competitor names, pricing objections, "cancel")
Call highlights: auto-marks key moments in transcript (objections, questions, competitor mentions)
Manager coaching: review AI highlights without listening to full recordings — scale quality review

Tip: Conversation Intelligence solves the "call quality black box" problem. Managers traditionally could only review sampled calls. AI analysis makes it possible to review all calls at scale.

What is Relationship Analytics?

Relationship Analytics analyses communication between sales reps and customers to provide health scores and engagement insights.

Feature	Description
Relationship health score	A/B/C/D grade based on interaction frequency and recency
Activity analytics	Email open rates, meeting frequency, response times, last contact date
Who knows whom	Identifies colleagues with existing relationships to customer contacts
Relationship risk	Flags opps/accounts where engagement has dropped — risk of going dark
LinkedIn integration	Shared connections, job changes, company news from Sales Navigator

5. Sales Accelerator & Sequences

What is the Sales Accelerator?

The Sales Accelerator is a unified productivity workspace for inside sales teams — a prioritised worklist and focused working environment.

Worklist: all records requiring action today, ordered by priority
Up next widget: next recommended action for each record
Inline communication: send emails, make calls directly from the worklist
Priority scores: AI-prioritised — highest-scoring leads and opps appear first
Skip and snooze: reps snooze records to re-appear later or skip sequence steps with a reason

Tip: Sales Accelerator removes context switching — reps work through their entire day from one focused interface without jumping between records. The answer to "how do you improve inside sales productivity."

What are Sales Sequences (Cadences)?

Sales Sequences are automated, time-based action plans assigned to Leads or Opportunities guiding reps through consistent outreach activities.

Example sequence: "New Enterprise Lead Outreach"
Day 1:  Email — Send personalised intro email (AI-drafted template)
Day 2:  Phone call — Follow up on email
Day 4:  LinkedIn connection request
Day 7:  Email — Send relevant case study
Day 10: Phone call — Discovery conversation request
Day 14: Task — Add to 90-day nurture campaign if no response

Sequence features:
→ Auto-creates activities on the record at the right time
→ Rep sees "Up Next" activity in Sales Accelerator
→ Completing activity early unlocks the next step immediately
→ If deal advances: sequence can be disconnected
→ Analytics: email open rates, response rates, meeting booking % by step

Sequence types:
→ Lead sequences: for new lead outreach
→ Opportunity sequences: for deal nurturing and follow-up
→ Account sequences: for customer success / renewal outreach

6. Forecasting & Goals

What is Sales Forecasting in D365 Sales?

Sales Forecasting predicts revenue for a period based on pipeline opportunities — rolled up through the sales hierarchy.

Forecast configuration:
→ Period: monthly / quarterly / yearly
→ Hierarchy: based on Manager field on User record
→ Forecast columns (configurable):
   Quota:     target assigned by manager
   Committed: deals rep is highly confident of closing this period
   Best Case: Committed + possible deals
   Won:       already closed-won in the period
   Pipeline:  all open deals in forecast period
   Gap:       Quota minus Won/Committed

Forecast categories on Opportunity (rep-managed):
Best Case  → possible close this period
Committed  → rep is highly confident this period
Omitted    → excluded (stalled or not this period)
Won        → auto-set on Close as Won
Lost       → auto-set on Close as Lost

Hierarchy rollup example:
Rep A: Committed $200K | Best Case $350K
Rep B: Committed $300K | Best Case $400K
Manager: Committed $500K | Best Case $750K
Director: sees all managers rolled up

Tip: Forecast category is rep-managed and separate from probability %. A rep can have a 70% probability opportunity marked "Omitted" from forecast if the deal has stalled. This gives managers realistic pipeline visibility.

What are Goals and Goal Metrics?

Goals allow managers to define revenue targets and track progress in real time.

Goal Metric: defines WHAT is measured
→ "Revenue Won" metric: measures Opportunity Actual Revenue (Won)
→ "New Logos" metric: counts new Accounts created from Won opps
→ Rollup fields: Actual (achieved), In Progress (open pipeline)

Goal:
→ Linked to a Goal Metric
→ Assigned to: User or Team
→ Period: monthly / quarterly / fiscal year
→ Target: $500,000 revenue Q1
→ Actual: auto-calculated from Won opps in period
→ In Progress: auto-calculated from open pipeline

Goal hierarchy:
Rep goals roll up → Manager goal → Director goal → VP goal
Each manager sees their team's aggregate vs target

Example:
Rep A: Q1 target $250K → actual $180K → 72% of quota
Rep B: Q1 target $300K → actual $320K → 107% of quota
Manager: Q1 target $550K → actual $500K → 91% of quota

7. Configuration, Security & Integration

How does the D365 Sales security model work?

Key security roles:
System Administrator  → full access, all configuration
System Customizer     → customise without data access
Sales Manager         → manage team records, reports, coaching
Salesperson           → manage own records, limited team visibility

Business Unit hierarchy:
Contoso Ltd (root BU)
  └── EMEA BU
       ├── UK BU → UK Sales Team
       └── DACH BU → DACH Sales Team

Security scope per role:
Account:     User scope → rep sees only accounts they own
Opportunity: BU scope   → rep sees all opps in their BU
Lead:        User scope → rep sees only their own leads

Field-level security:
→ Restrict Actual Revenue, Contract Terms, Discount Authority
→ Only Sales Managers and Directors see deal financials

Territory management:
→ Assign accounts to territories (geographic or industry-based)
→ Automatic assignment rules based on postal code, country, or account attributes
→ Territory membership drives which rep is auto-assigned new accounts

What are the key customisation points in D365 Sales?

Layer	Customisation
Forms	Customise Opportunity, Lead, Quote forms — add fields, sections, subgrids
Views	Configure list views — My Open Opps, Team Pipeline, Stale Deals
Business rules	Field show/hide/set/validate (e.g., hide Competitor field unless stage = Propose)
Business Process Flows	Custom sales stages matching org's sales methodology
Plugins	C# server-side logic (e.g., auto-assign territory on Account create)
Power Automate	Automated actions (approval flows, notifications, ERP sync)
Dashboards	Custom sales dashboards for rep, manager, executive views

What are the key D365 Sales integrations?

Integration	Description
D365 App for Outlook	Track emails/appointments to D365 records; Copilot for Sales in Outlook
Microsoft Teams	D365 records in Teams; Teams calls recorded via Conversation Intelligence
LinkedIn Sales Navigator	Embedded in Account/Contact/Lead/Opp forms — profile, InMail, connections
ERP (Business Central, SAP)	Sync products, price lists, orders, invoices between D365 and ERP
D365 Marketing / Customer Insights	Campaign-generated leads flow to D365 Sales; attribution tracking
Power BI	Pipeline reports, win/loss analysis, forecast accuracy on Dataverse data

8. Scenario-Based Questions

Scenario: Sales reps are not updating D365 — pipeline data is stale. How do you fix this?

Root cause: reps work in Outlook and Teams, not D365. Logging activity is manual and feels like admin overhead.

Solutions:

Copilot for Sales in Outlook: email auto-capture logs activity to D365 automatically — zero manual effort. Reps see CRM context in their inbox.
Teams integration: link Teams meetings to D365 opps. Post-meeting, Copilot generates summary and suggests CRM updates — rep approves with one click.
Sales Accelerator: reps start their day in a prioritised worklist driven by D365 — making D365 where work happens, not a separate admin task.
Sales Sequences: auto-create activities on records — rep's next action is always defined, reducing the "what should I do?" friction.
Required fields: make Close Date and Forecast Category required on Opportunity. Keep required fields minimal — every unnecessary required field increases friction.
Manager accountability: managers review pipeline in D365 weekly 1:1s. Stale records become visible and uncomfortable.

Tip: CRM adoption is both a process and technology problem. Copilot and auto-capture reduce friction. Manager behaviour drives compliance. Both are required.

Scenario: Design a D365 Sales implementation for a B2B SaaS company with field and inside sales teams.

Architecture:

Business units: Field Sales BU (enterprise, >500 employees) and Inside Sales BU (SMB, ≤500)
Lead routing: inbound website leads → Power Automate → auto-assign based on company size
Sales Processes (BPF):
- Field sales: 6-stage enterprise BPF (Qualify → Discover → Technical Validation → Business Case → Negotiate → Close)
- Inside sales: 4-stage velocity BPF (Qualify → Demo → Proposal → Close)
Products & Pricing: SaaS tiers (Starter/Growth/Enterprise), annual/monthly price lists, volume discount lists (≥50 seats: 10% off)
Sequences: inside sales sequences for high-velocity outreach (Day 1 email → Day 2 call → Day 4 follow-up)
AI: Predictive Lead Scoring for inside reps' worklist prioritisation. Conversation Intelligence for inside rep call coaching.
Forecasting: quarterly forecast by team (Inside vs Field) rolled up to VP Sales. Separate quotas per team.
Copilot for Sales: Outlook + Teams integration for both teams — email capture, meeting prep, post-meeting CRM updates.

Scenario: Configure approval workflows for discounts above 20% on quotes.

Add "Total Discount %" calculated field to the Quote form

Power Automate approval flow triggered on Quote status = "Pending Approval":

Condition: If Total Discount % > 50 → escalate to VP Sales + FinanceCondition: 
If Total Discount % > 35 → escalate to Sales DirectorCondition: 
If Total Discount % > 20 → send to Sales ManagerCondition: 
If Total Discount % ≤ 20 → auto-approveOn approval: 
set Quote status = "Approved", notify repOn rejection: 
set status = "Draft", notify rep with manager comment

Business rule: lock discount field when Quote status = "Activated" — prevents post-approval changes
Audit trail: approval history stored as activity records on the Quote — full visibility of approver, date, and decision

Scenario: Pipeline reviews show opportunities stalling at the Proposal stage. How do you diagnose and fix it?

Diagnose:

Power BI: "Days in stage" report — if Proposal stage is 3x other stages, confirmed bottleneck
Win/loss analysis: filter lost opps that stalled in Proposal. Common reasons: "Pricing" and "No budget approval"
Conversation Intelligence: review call recordings from Proposal-stage opps — identify common unaddressed objections
BPF compliance: check if reps are progressing to Proposal without completing Develop stage requirements (budget confirmed? decision maker identified?)

Fix:

Make "Budget approval process identified" a required step in the Develop stage BPF
Add Proposal stage sequence: auto-reminder every 3 days to follow up on proposal
Knowledge base of objection handling for common pricing challenges
Automatic alert when opportunity spends >14 days in Proposal → supervisor notification
"Price sensitivity" field on Opportunity — flag deals where pricing is a known risk for proactive manager coaching

Scenario: How do you implement territory management for a global sales org?

Requirement: APAC, EMEA, and AMER regions. Each region has country-level territories. Accounts auto-assigned to the right rep.

Create territory hierarchy:

Global Territory├── AMER│    ├── US-West (rep: John)│    ├── US-East (rep: Sarah)│    └── Canada (rep: Mike)├── EMEA│    ├── UK + Ireland (rep: Emma)│    └── DACH (rep: Klaus)└── APAC     ├── ANZ (rep: David)     └── ASEAN (rep: Priya)

Auto-assignment rules: Power Automate flow on Account Create — check address1_country → assign to matching territory member
Security: Salesperson role with BU scope scoped to their territory BU — only sees their territory's accounts/opps
Reporting: pipeline and quota attainment filterable by territory in Power BI dashboard
Territory changes: reassignment flow when territory boundaries change — bulk update Account ownership via Power Automate

9. Cheat Sheet — Quick Reference

Sales Entity Lifecycle

Lead (unqualified):
  statecode: Open(0) / Qualified(1) / Disqualified(2)
  Qualify → creates Contact + Account + Opportunity
  Disqualify → status reasons: Lost / No Longer Interested / Cannot Contact

Opportunity:
  statecode: Open(0) / Won(1) / Lost(2)
  Status reasons (Open): In Progress / On Hold
  Close Won → creates blank Order (rep adds products)
  Close Lost → requires loss reason (make it required!)

Quote:
  Status: Draft → Active → Won/Closed/Revised

Order:
  Status: Active → Fulfilled → Cancelled

Invoice:
  Status: Active (unpaid) → Paid → Cancelled

Forecasting Quick Reference

Forecast categories (rep-managed):
Best Case  → possible close this period
Committed  → highly confident this period
Omitted    → excluded (stalled or out of period)
Won        → auto-set on Close as Won
Lost       → auto-set on Close as Lost

Forecast columns (admin-configured):
Quota     | Won | Committed | Best Case | Pipeline | Gap to Quota

Expected Revenue formula:
Expected = Estimated Value × Probability %
($500K × 75%) = $375K expected

Hierarchy: Rep → Manager → Director → VP
All levels see their team's aggregate rolled up in real time

AI Features Summary

Copilot for Sales (add-on):
→ Email drafting in Outlook (CRM-contextual)
→ Meeting prep brief before Teams calls
→ Meeting summary + action items after Teams calls
→ Opportunity summary (one click)
→ CRM updates from Outlook/Teams

Predictive Lead Scoring (Sales Premium):
→ 0-100 score, A/B/C/D grade
→ Trained on org's own historical Won/Lost leads
→ Prioritises Sales Accelerator worklist

Predictive Opportunity Scoring (Sales Premium):
→ 0-100 score, A/B/C/D grade
→ Trained on org's own Won/Lost opportunities
→ Gets more accurate over time

Conversation Intelligence (Enterprise+):
→ Auto-records and transcribes Teams sales calls
→ Talk-to-listen ratio, keyword tracking
→ AI highlights (objections, questions, competitors)
→ Manager coaching at scale

Relationship Analytics (Enterprise+):
→ Relationship health score A/B/C/D
→ Engagement drop alerts
→ Who-knows-whom for warm introductions
→ LinkedIn integration (with Sales Navigator)

Key D365 Sales KPIs

Win Rate         = Won Opps / Total Closed Opps × 100
Avg Deal Size    = Total Won Revenue / Won Opp Count
Sales Cycle Len  = Avg days from Lead qual to Close Won
Pipeline Coverage= Pipeline Value / Quota Target (ideal: 3-4×)
Quota Attainment = Actual Revenue / Quota × 100
Forecast Accuracy= Actual Revenue / Committed Forecast × 100
Lead Conversion  = Qualified Leads / Total Leads × 100
Stage Conversion = Opps entering stage / Opps exiting Won

Top 10 Tips

Lead vs Opportunity — Lead = potential interest, no customer record. Opportunity = qualified deal with Account and Contact. Qualification is the data quality gate. Never skip it.
Loss reasons are required fields — make loss reason mandatory on Close as Lost. Optional fields are ignored by reps and make win/loss analysis meaningless.
BPF stage data is reportable — Business Process Flow stage, days in stage, and conversion rates are stored in Dataverse and fully reportable in Power BI. This is a differentiated insight.
Forecast category ≠ probability — forecast category is rep-managed (Committed/Best Case/Omitted) and separate from the % probability field. A 70% probability opp can be Omitted from forecast if stalled.
Copilot for Sales = adoption accelerator — reps work in Outlook and Teams. Copilot for Sales brings CRM into their workflow. This is the answer to every "how do you improve CRM adoption" question.
Predictive scoring uses YOUR data — models are trained on your org's historical won/lost records, not generic industry data. They improve over time. This is a key differentiator vs. rules-based scoring.
Quote Revise, not Edit — once a Quote is Active (sent to customer), you cannot edit it. Use Revise to create a new Draft version. The Active quote is automatically closed.
Sales Accelerator for inside sales — one focused worklist driven by sequences and AI scores. The answer to any inside sales productivity question.
Conversation Intelligence scales quality review — managers can't listen to all calls. AI highlights, talk-to-listen ratio, and keyword alerts make it possible to coach all reps, not just sampled ones.
Goals roll up the hierarchy — rep goals auto-roll up to manager → director → VP. This gives real-time quota attainment visibility at every level of the org without manual aggregation.

Thursday, April 30, 2026

SharePoint Classic Blank-Fallback Redirect Page via CEWP

SharePoint Classic — Blank-Fallback Redirect Page via CEWP

Query Parameter Routing · jQuery · Content Editor Web Part · Site Assets · window.top

What This Does and Why You Need It
How It Works — Logic Flow
The Redirect Map
Behaviour Reference
Full Script
Deployment Steps
Technical Notes
Cheat Sheet — Quick Reference

1. What This Does and Why You Need It

The problem

In SharePoint classic, there is no built-in way to route a user to different pages based on a URL parameter. If you are linking to SharePoint from an external system — a PLM tool, a Power Automate notification, an email — and you want one stable URL that fans out to different destinations depending on a short code, you need to build it yourself.

This script gives you exactly that:

A single SharePoint page (/SitePages/Redirect.aspx)
A ?q= query parameter that maps to any destination URL
Instant redirect when a valid key is found
A completely blank white screen when no key matches — no error, no broken layout, nothing

Why client-side?

SharePoint Online does not give you access to web.config or IIS redirect rules. Without a custom SPFx solution or an Azure Function in front, a lightweight jQuery script loaded via the Content Editor Web Part is the most practical approach.

2. How It Works — Logic Flow

Page loads
     ↓
Read window.top.location.search → extract ?q= parameter
     ↓
Look up value in redirectMap object
     ↓
Match found?
  YES → window.top.location.replace(url)   ← instant redirect, no history entry
  NO  → $(document).ready → hide all body children → white background

The key detail: the redirect fires before the DOM renders. When a valid ?q= value is present, the user never sees the SharePoint page at all — they land directly on the destination.

When no match is found, the script waits for $(document).ready and then hides every child element on the parent page, leaving a clean white screen.

3. The Redirect Map

The redirect map is a plain JavaScript object. Keys are short identifiers (numbers, codes, slugs). Values are full absolute URLs.

var redirectMap = {
    "1": "https://[tenant].sharepoint.com/SitePages/Page1.aspx",
    "2": "https://[tenant].sharepoint.com/SitePages/Page2.aspx"
};

To add a new destination, add a new key-value pair:

"3": "https://[tenant].sharepoint.com/SitePages/NewTarget.aspx"

Keys can be any string — numbers work well for short external references. Values must be full absolute URLs.

4. Behaviour Reference

URL	Result
`/SitePages/Redirect.aspx?q=1`	Redirects to destination 1
`/SitePages/Redirect.aspx?q=2`	Redirects to destination 2
`/SitePages/Redirect.aspx`	Blank white page
`/SitePages/Redirect.aspx?q=99`	Blank white page (no match)

5. Full Script

Save this as an .html file (e.g. redirect-handler.html). Upload it to your Site Assets library. Point the Content Editor Web Part's ContentLink property to its URL.

<!DOCTYPE html>
<html>
<head>
    <style>
        body { margin: 0; padding: 0; background-color: #fff; }
    </style>
</head>
<body>

<script src="https://code.jquery.com/jquery-3.7.1.min.js"></script>
<script type="text/javascript">

    // Redirect map — add or change entries here as needed
    var redirectMap = {
        "1": "https://[TENANT].sharepoint.com/SitePages/Page1.aspx",
        "2": "https://[TENANT].sharepoint.com/SitePages/Page2.aspx"
    };

    // Read ?q= from URL immediately (before DOM renders)
    // window.top used because this script runs inside a CEWP iframe
    var params = new URLSearchParams(window.top.location.search);
    var qValue = params.get("q");

    if (qValue && redirectMap[qValue]) {
        // Redirect instantly — page content never renders
        // replace() avoids adding the redirect page to browser history
        window.top.location.replace(redirectMap[qValue]);

    } else {
        // No match — hide all SharePoint content, show blank white page
        $(document).ready(function () {
            $(window.top.document).find("body").children().hide();
            $(window.top.document.body).css({
                "margin": "0",
                "padding": "0",
                "background-color": "#ffffff",
                "overflow": "hidden"
            });
        });
    }

</script>
</body>
</html>

6. Deployment Steps

Replace [TENANT] placeholders in the redirect map with your actual SharePoint site URLs.
Save the file as redirect-handler.html (or any name you prefer).
Upload the file to your Site Assets library.
Copy the full URL of the uploaded file (e.g. https://[tenant].sharepoint.com/SiteAssets/redirect-handler.html).
Open the SharePoint classic page (Redirect.aspx) in edit mode.
Add a Content Editor Web Part to the page.
Open the Web Part tool pane → set the ContentLink property to the file URL from step 4.
Save and publish the page.
Test with ?q=1, ?q=2, and with no parameter.

Tip: To add more redirect destinations later, just edit the HTML file in Site Assets. No changes to the SharePoint page or Web Part are needed.

7. Technical Notes

Why window.top?

The Content Editor Web Part loads your HTML file inside a hidden <iframe>. The SharePoint chrome — suite bar, page title, content zones — lives on the parent frame. Without window.top, the script can only see the tiny iframe it's running in, not the actual page. All DOM manipulation and URL reads must go through window.top.

Why location.replace() instead of .href?

window.top.location.replace(url) replaces the current history entry rather than pushing a new one. If the user hits the browser back button after being redirected, they will not loop back through the redirect page — they will land on the page they were at before.

Why host the file in Site Assets?

SharePoint Online blocks inline <script> tags inside CEWP rich text fields. The only way to run JavaScript through a CEWP is to upload an external HTML file and reference it via the ContentLink property. Site Assets is the conventional library for these files — it is accessible to all site members by default.

Cross-origin requirement

window.top access requires the CEWP iframe and the parent page to share the same origin. Since both the HTML file (Site Assets) and the SharePoint page are on the same tenant, this is never a problem in practice. It would break if the file were hosted on a different domain.

Browser history note

The redirect uses location.replace(), so the redirect page itself does not appear in the browser's back-navigation history. Destination pages behave normally.

Warning: This approach uses DOM manipulation via window.top, which depends on the CEWP iframe pattern specific to SharePoint classic pages. It will not work on modern SharePoint pages, which do not support the Content Editor Web Part.

8. Cheat Sheet — Quick Reference

File locations

Item	Location
Script file	`/SiteAssets/redirect-handler.html`
SharePoint page	`/SitePages/Redirect.aspx`
Web Part type	Content Editor Web Part (CEWP)
Web Part zone	LeftColumn
jQuery version	3.7.1 (CDN)

Key concepts

CEWP (Content Editor Web Part)
→ Classic SharePoint web part
→ Loads external HTML via ContentLink property
→ Creates a hidden iframe — script runs inside it

window.top
→ Reference to the parent (SharePoint) frame from inside the CEWP iframe
→ Required for all URL reads and DOM manipulation

location.replace(url)
→ Redirect without adding to browser history
→ Use instead of location.href for redirect pages

redirectMap
→ Plain JS object: { "key": "destination-url" }
→ Add entries here when new destinations are needed
→ No other changes required

Troubleshooting

Symptom	Likely cause	Fix
Page loads normally, no redirect	Script file not loading	Check ContentLink URL is correct and file exists in Site Assets
Redirect works but page briefly flashes	DOM renders before script runs	Expected — redirect fires before DOM in all modern browsers; flash is negligible
Blank page not fully white	CSS from SharePoint theme overriding	Ensure `background-color: #ffffff` and `overflow: hidden` are applied to `window.top.document.body`
Script errors in console	Cross-origin block	Confirm HTML file is on the same SharePoint tenant, not an external domain
Works in Chrome, not Edge/Firefox	Browser security policy difference	Verify same-origin requirement; check browser console for specific error

Top 5 tips

ContentLink, not rich text — always reference the HTML file via the ContentLink property, never paste script into the CEWP rich text editor. SharePoint Online strips inline scripts.
window.top for everything — any reference to the parent page (URL, DOM) must go through window.top. Plain document or window only reaches the CEWP iframe.
location.replace() not .href — prevents the redirect page from appearing in browser history. Users can navigate back cleanly.
Extend via list, not hardcode — if destinations change frequently, consider loading the redirect map from a SharePoint list via REST API instead of hardcoding it in the file.
Classic pages only — this technique relies on the Content Editor Web Part, which is not available on modern SharePoint pages. For modern pages, use a SPFx web part or redirect via Power Automate.

Wednesday, April 29, 2026

Dynamics 365 Customer Service Complete Guide

Dynamics 365 Customer Service — Complete Guide

Case Management · Omnichannel · Knowledge Base · AI Copilot · Unified Routing · SLA · Scenarios · Cheat Sheet

Core Concepts — Basics
Case Management — Deep Dive
Omnichannel for Customer Service
Knowledge Management & AI Copilot
Unified Routing & Skills
SLA & Entitlements
Analytics & Reporting
Customisation & Integration
Scenario-Based Questions
Cheat Sheet — Quick Reference

1. Core Concepts — Basics

What is Dynamics 365 Customer Service and what does it do?

Dynamics 365 Customer Service is a Microsoft customer relationship and service management application built on Dataverse. It enables organisations to manage customer support operations across multiple channels.

Core capabilities:

Case management: create, track, route, escalate, and resolve customer issues
Omnichannel: handle conversations across chat, email, voice, SMS, social media in a unified agent workspace
Knowledge management: author, publish, and surface relevant knowledge articles to agents and customers
SLAs: define and enforce response/resolution time commitments with automatic escalations
AI and Copilot: agent assist, sentiment analysis, case summarisation, and smart routing
Customer Service workspace: unified agent desktop combining all channels and case management

What are the main tables (entities) in Dynamics 365 Customer Service?

Table	Description
Case (incident)	Central entity — represents a customer issue or service request
Account	Business/organisation customer
Contact	Individual customer
Queue	Work item bucket — cases and activities routed here for agents
Queue Item	Links a work item (case, email, chat) to a queue
Knowledge Article	Published support article for agents and customers
Entitlement	Defines support terms — number of cases, response SLA
SLA	Defines KPIs (first response time, resolution time) and breach actions
Activity	Email, Phone Call, Task, Chat, Voice — interactions linked to a case

What is the Customer Service workspace vs Customer Service Hub?

Customer Service Hub: traditional model-driven app for case management. Provides clean interface for managing cases, knowledge articles, and queues. Does NOT include Omnichannel channels (chat, voice, SMS).

Customer Service workspace: modern unified agent desktop. Includes all Customer Service Hub features PLUS Omnichannel channels — live chat, voice, SMS, social messaging — all in a single tabbed multisession interface.

Tip: For any new D365 Customer Service implementation, Customer Service workspace is the recommended agent interface. Customer Service Hub is used by administrators and supervisors for configuration and oversight.

What are the D365 Customer Service licensing tiers?

Licence	Key Features
Customer Service Professional	Core case management, knowledge base, SLAs, basic routing. No Omnichannel.
Customer Service Enterprise	All Professional + advanced routing (Unified Routing), AI features, Copilot, analytics
Omnichannel add-on	Live chat, SMS, social messaging, voice — on top of Enterprise
Copilot for Service	AI assistant for agents — case summarisation, response drafting, knowledge search

Warning: Omnichannel is a separate add-on — not included in base Customer Service Enterprise. Voice channel requires an additional Azure Communication Services resource and licensing.

2. Case Management — Deep Dive

What is the Case lifecycle and what are the key statuses?

Case Status (statecode):
Active (0)    → Case is open and being worked
Resolved (1)  → Case has been resolved — resolution logged
Cancelled (2) → Case cancelled (duplicate, invalid, customer withdrew)

Status Reasons under Active:
In Progress         → agent is actively working the case
On Hold             → waiting for customer or third party
Waiting for Details → waiting for customer to provide more info
Researching         → agent is investigating

Status Reasons under Resolved:
Problem Solved       → issue fixed
Information Provided → customer needed guidance
Cancelled            → not a valid issue

Case Lifecycle:
[Created] → [Assigned/Routed to Queue] → [In Progress]
→ [On Hold if awaiting info] → [Resolved] → [Closed after X days]

Key rules:
→ SLA KPIs start when case is created
→ SLA pauses when Status Reason = On Hold (configurable)
→ Resolution records time spent, resolution type, and description
→ Closed cases cannot be re-opened — create new case or follow-up

What are Queues in D365 Customer Service?

Queues are work item buckets holding cases and activities waiting to be picked up by agents.

Queue types:

Type	Visibility	Use Case
Public	All agents with access	General team queues
Private	Specific users/teams only	Specialist team queues
Personal	Each user's own queue	Individual workload

Queue workflow:
Case created → assigned to Queue (manually or routing rule)
Agent opens Queue → sees all items → clicks "Pick" to take ownership
OR: supervisor assigns directly to agent (bypasses queue pick)

Queue Item states:
Queued      → waiting to be picked up by an agent
In Progress → assigned to and being worked by an agent

Tip: In Omnichannel, queues are extended to handle live conversations (chat, voice, SMS) in addition to cases — the same queue concept applies across all work types.

What is the Parent-Child Case relationship?

Parent-Child cases allow one complex case to be broken into sub-cases worked by different teams in parallel.

Use case: Customer reports complete system failure

Parent case: "System Outage — Customer X" (Account Manager)
  Child case 1: "Network investigation" → Network team queue
  Child case 2: "Database connectivity" → DBA team queue
  Child case 3: "Application error" → Dev team queue

Status sync options:
→ Auto-resolve parent when ALL child cases are resolved
→ Or: manual — parent managed independently

SLA: each child case has its own SLA clock
Customer view: sees one parent case — internal complexity hidden

What are the Case subject tree and categories?

The Subject tree is a hierarchical classification structure for cases — enabling consistent categorisation, routing, and analytics.

Subject tree example:
Products
  └── Product A
       ├── Technical Issues
       │    ├── Installation
       │    └── Performance
       └── Billing Issues
            ├── Invoice Query
            └── Refund Request
Services
  └── Professional Services
       └── Onboarding

Benefits:
→ Consistent case classification across teams
→ Routing rules: IF subject = 'Billing Issues' → Finance queue
→ Analytics: case volume and resolution time by topic
→ Knowledge article association: link articles to subject areas

3. Omnichannel for Customer Service

What is Omnichannel and what channels does it support?

Omnichannel for Customer Service is the real-time customer engagement layer routing customer conversations from multiple digital channels to agents in a unified desktop.

Channel	Description
Live Chat	Web chat widget embedded on websites or portals
Voice	Inbound/outbound phone calls via Azure Communication Services
SMS	Two-way text messaging
Microsoft Teams	Internal escalation from Teams to D365 agent
Email	Enhanced email routing within agent workspace
Facebook Messenger	Social messaging
WhatsApp	Messaging via Business API
Twitter/X, WeChat, LINE, Telegram	Via third-party providers
Custom channel	Direct Line API integration for any custom channel

Tip: All channels surface in the same Customer Service workspace — agents see one unified inbox regardless of channel.

What is the Omnichannel agent workspace and its key features?

Active Conversation screen: central workspace — customer conversation alongside customer summary (name, account, open cases, recent history)
Multisession: agents handle multiple conversations simultaneously via tabbed sessions
Customer 360 summary: contact details, account info, recent cases, sentiment score, conversation history
Communication panel: channel-specific interaction (chat transcript, call controls, email compose)
Productivity pane: agent assist — knowledge search, similar cases, AI-suggested responses, Copilot
Presence management: agent sets availability (Available, Busy, Do Not Disturb, Away) — routing only assigns to available agents
Supervisor dashboard: real-time monitoring of agent workloads, queue depths, sentiment, SLA compliance

What is agent capacity in Omnichannel?

Agent capacity defines the maximum workload an agent can handle simultaneously. Each work type consumes capacity units.

Example capacity configuration:
Agent total capacity: 100 units

Work item costs:
Live Chat:   20 units per conversation
Voice call:  50 units (prevents multi-tasking during calls)
SMS:         10 units per conversation
Case:         5 units per case

Concurrent handling:
→ 1 voice (50) + 2 SMS (20) + 2 cases (10) = 100 (full)
→ 5 chats (100) = 100 (full)
→ 4 chats (80) + 2 SMS (20) = 100 (full)

When capacity = 0: no new assignments
When presence = Busy: capacity treated as 0 for new work

Tip: Configure voice capacity close to total agent capacity to prevent agents receiving chat while on a call.

How does the Copilot Studio bot-to-human handoff work in Omnichannel?

Customer journey:
1. Customer starts chat on website
2. Copilot Studio bot handles conversation:
   → Answers FAQs from knowledge base
   → Collects customer details (name, account, issue type)
   → Resolves simple issues (password reset, account balance)
3. Bot cannot resolve → escalates to D365 Omnichannel

Context passed to agent:
→ Customer name, email, account ID (collected by bot)
→ Issue category (determined by bot intent recognition)
→ Full bot conversation transcript
→ Bot escalation reason ("Cannot resolve: Complex billing issue")

D365 uses context to:
→ Pre-populate case fields (customer, subject, description)
→ Route to correct queue based on bot-determined category
→ Show agent a summary of the bot interaction

Result: customer never repeats themselves — agent continues from
exactly where the bot left off

Tip: Bot-to-human escalation with full context handoff is one of the most commonly asked D365 CS architecture scenarios in senior .

4. Knowledge Management & AI Copilot

What is the Knowledge Base lifecycle?

Knowledge Article statuses:
Draft → In Review → Approved → Published → Expired

Draft:     Author creates article — title, content, keywords, related products
In Review: Submitted to knowledge manager for review
Approved:  Reviewed and approved — not yet visible to external users
Published: Live — visible to agents AND customers on self-service portal
Scheduled: Auto-publishes on a future date
Expired:   Past expiry date — auto-unpublished, needs renewal

Key features:
→ Versioning: each edit = new version, previous versions preserved
→ Translation: articles translated into multiple languages
→ Feedback: agents/customers rate articles (helpful/not helpful)
→ Analytics: views, likes, dislikes, cases linked to article
→ Internal vs external: internal-only (agents) or external (portal)
→ Keywords: improve search relevance
→ Related articles: link related content for agent context

How does Copilot for Customer Service work?

Copilot is an AI assistant in the agent productivity pane powered by Azure OpenAI.

Capability	Description
Ask a question	Searches knowledge base + similar cases → synthesised answer with citations
Draft a response	Generates contextually appropriate reply based on conversation + KB
Case summary	One-click AI summary: customer issue, steps taken, current status
Conversation summary	Auto-generates end-of-conversation notes for case records
Suggested articles	Surfaces most relevant KB articles based on case context

Tip: Copilot for Customer Service measurably reduces Average Handling Time (AHT) and improves First Contact Resolution (FCR). Know its capabilities for any AI-focused question.

What is real-time sentiment analysis?

Real-time sentiment analysis uses Azure AI to analyse customer messages in live chat or voice conversations and display a sentiment score — updated as the conversation progresses.

Sentiment levels: Positive, Slightly Positive, Neutral, Slightly Negative, Negative

How it's used:

Supervisor sees sentiment for ALL active conversations in the Supervisor Dashboard
Agent sees their own conversation's sentiment in the conversation panel
When sentiment drops to Negative: supervisor can be alerted and may intervene
Sentiment stored on conversation record — available for historical analysis

5. Unified Routing & Skills

What is Unified Routing and how does it work?

Unified Routing is the intelligent work distribution engine routing both cases (record routing) and Omnichannel conversations to the most appropriate queue and agent.

Unified Routing pipeline:

Work item arrives (case created OR conversation started)
        ↓
[Classification] — AI or rule-based
  → Set: priority, skills required, category, sentiment, language
        ↓
[Route to Queue] — routing rules
  Rule: IF language = 'French' → France Support Queue
  Rule: IF priority = 'Critical' → Tier3 Escalation Queue
  Rule: IF topic = 'Billing' → Finance Queue
  Rule: IF entitlement_tier = 'Gold' → Gold Priority Queue
        ↓
[Assignment] — assignment method
  1. Highest capacity → assign to agent with most available capacity
  2. Round robin → distribute evenly across available agents
  3. Least active → agent with fewest active sessions
  4. Skills-based → match required skills to agent skill profile

Tip: Unified Routing replaces both the older basic routing rules for cases AND handles real-time Omnichannel conversation routing in a single engine. Always use Unified Routing for new implementations.

What are Skills and how do you implement skills-based routing?

Skills setup:
1. Define skill types: Language, Product Knowledge, Technical Level
2. Create skills: French (10), SAP ERP (8), Network+ (9), Level2 (7)
3. Assign skills to agents with proficiency (1-10):
   Maria: French(10), SAP ERP(8), Level2(7)
   John:  English(10), Network+(9), Level1(5)

Skills classification on work item:
AI-based: NLP analyses case content → auto-assigns required skills
  → Detects language → requires Language skill
  → Detects "SAP" keyword → requires SAP ERP skill
Rule-based: IF product = 'SAP' THEN require SAP ERP skill ≥ 7

Assignment with skills:
→ Exact match: agent has ALL required skills at required proficiency
→ Closest match: if no exact, find closest skill profile
→ Skill relaxation: after 5 min, lower proficiency requirement
                    after 10 min, relax to any available agent

Tip: Skill relaxation is critical to prevent long wait times. Balance quality (exact skill match) with responsiveness (relaxation over time).

What are the Omnichannel Supervisor capabilities?

The Supervisor Dashboard provides real-time visibility into:

View	Metrics
Conversations	Active conversations, status, channel, sentiment, duration, agent
Agents	Agent presence, active conversations, capacity utilised
Queues	Queue depth, average wait time, longest waiting item
Ongoing conversations	Ability to monitor, assign, transfer, or join conversations

Supervisor actions:

Monitor: silently observe a conversation (agent unaware)
Barge-in: join an active conversation (agent and customer see supervisor join)
Transfer: move a conversation from one agent to another
Assign: pull a queued item directly to a specific agent

6. SLA & Entitlements

What are SLAs in D365 and what are the two types?

Standard SLA: basic SLA with a single KPI. When breached, a warning flag shows on the case. No automatic actions.

Enhanced SLA (recommended): supports multiple KPIs, pause/resume, and automatic breach actions.

Enhanced SLA example — "Gold Customer SLA":

KPI 1: First Response By
  Warning: 30 minutes → action: email agent's manager
  Failure: 1 hour → action: escalate to Tier2, email customer

KPI 2: Resolve By
  Warning: 6 hours → action: alert supervisor
  Failure: 8 hours → action: escalate to manager, notify account team
  Pause condition: Status Reason = "Waiting for Details"
  Resume: when Status Reason changes back to "In Progress"

SLA timer on case form:
→ Countdown timer: time remaining until breach
→ Amber indicator: warning threshold reached
→ Red indicator: SLA breached
→ Paused indicator: case on hold

Warning: Always use Enhanced SLA for production. Standard SLA lacks pause/resume and automated breach actions. Enhanced SLA is the current standard.

What are Entitlements?

Entitlements define the support terms for a customer — how many cases they are entitled to, applicable SLA, and which channels they can use.

Entitlement structure:
Entitlement → linked to Account or Contact
  Allotment type: Number of cases (e.g., 10 per year)
                  OR Hours (e.g., 40 hours per year)
  Total terms: 10
  Remaining terms: auto-decremented when case is created
  Start/end date: validity period
  Associated SLA: Gold SLA (applied automatically to cases)
  Channels: Phone + Chat + Email (Gold) or Email only (Bronze)

When case created for customer with entitlement:
→ D365 auto-associates the entitlement to the case
→ Remaining terms decremented by 1
→ When terms = 0: agent sees warning — entitlement exhausted
→ Supervisor can override and continue or reject new case

Tip: Entitlements are the bridge between sales contracts and service delivery — they ensure customers receive exactly what they paid for. Agents see entitlement status directly on the case form.

7. Analytics & Reporting

What analytics are available in D365 Customer Service?

Built-in Power BI dashboards:

Dashboard	Key Metrics
Summary	Total cases, AHT, FCR rate, CSAT, SLA compliance
Agent	Cases handled, avg resolution time, CSAT, SLA compliance per agent
Queue	Avg wait time, queue depth, abandon rate, longest waiting item
Omnichannel	Conversations by channel, abandonment, avg conversation time, sentiment trends
Knowledge	Article views, likes/dislikes, articles linked to resolved cases
Bot	Self-service deflection rate, escalation rate, bot CSAT

Key KPIs:

CSAT  → Customer satisfaction score (post-resolution survey rating)
FCR   → First Contact Resolution % (resolved without re-open or follow-up)
AHT   → Average Handling Time (total agent time per case/conversation)
ASA   → Average Speed of Answer (arrival to agent assignment time)
Abandon Rate → % customers who left queue before being answered
SLA Compliance → % cases resolved within SLA target

What is Customer Service Insights?

Customer Service Insights provides AI-driven analytics identifying topics driving case volume and opportunities to reduce it.

Topic clustering: AI groups similar cases into topics automatically — no manual categorisation
Impact analysis: topics with highest volume, longest resolution time, or worst CSAT
Emerging issues: alerts when a new topic suddenly spikes in volume — early warning for product issues
Deflection opportunities: identifies topics where knowledge articles or chatbot could deflect live agent contacts

8. Customisation & Integration

What are the key customisation points in D365 Customer Service?

Layer	Customisation
Forms	Customise Case, Contact, Account forms — add/remove fields, sections, tabs
Views	Configure list views for queues, cases, knowledge articles
Business rules	Field show/hide/set/validate logic (client-side or server-side)
Business process flows	Stage-based guidance for agents working complex cases
Plugins	C# server-side logic on case create/update (e.g., auto-assign, validation)
Power Automate flows	Automated actions triggered by D365 events (SLA breach, case status change)
PCF controls	Custom UI components on case forms
API	Dataverse Web API for external system integration

How do you integrate D365 Customer Service with external systems?

Common integration patterns:

Dataverse Web API: CRUD operations on cases, contacts, accounts from external systems
Power Automate: event-driven integration — when case created → notify Slack/Teams, update ERP
Webhooks: real-time push notifications to external systems on D365 events
Azure Service Bus: reliable async messaging for high-volume case creation from external portals
Embedded experience: embed D365 widgets (chat, case history) in external portals via iFrame or JS API
CTI (Computer Telephony Integration): connect third-party phone systems to Omnichannel via Channel Integration Framework (CIF)

What is the Channel Integration Framework (CIF)?

CIF is a JavaScript API framework that allows third-party telephony and communication providers to integrate with the D365 Customer Service workspace. It provides:

CIF v1: Single-session — one communication provider in the side panel
CIF v2: Multi-session — multiple providers, integrates with Omnichannel routing

Use cases:

Connect existing Avaya, Cisco, Genesys, or Five9 phone systems to D365
Surface caller information (screen pop) in D365 before agent answers
Enable click-to-call from D365 records
Log call activities automatically to case records

9. Scenario-Based Questions

Scenario: Design a D365 Customer Service solution for a bank with Gold/Silver/Bronze customer tiers.

Architecture:

Entitlements per tier:
- Gold: unlimited cases, phone + chat + email, 1h first response / 4h resolution
- Silver: 20 cases/year, chat + email, 4h first response / 24h resolution
- Bronze: 5 cases/year, email only, 24h first response / 72h resolution
Enhanced SLAs: three SLAs with appropriate KPIs and breach actions. Auto-associate via entitlement.
Queues: Gold Priority Queue, Silver Queue, Bronze Queue — segregated so Gold is never affected by Bronze volume.
Unified Routing rule: check entitlement tier on case creation → route to tier-appropriate queue → assign with highest capacity method.
Channels: Gold gets Omnichannel (chat + phone). Silver/Bronze get email only.
Agent skills: senior agents tagged "Gold" skill → assigned to Gold queue. Junior agents handle Bronze.
Reporting: SLA compliance by tier. Escalation alerts when Gold SLA approaching breach.

Scenario: A case is stuck in queue for 2 hours without being picked up. How do you handle this?

Prevention (proactive):

SLA breach actions: configure "First Response By" KPI — at 1h warning: email queue manager. At 2h breach: auto-escalate to supervisor, change priority to Critical.
Power Automate escalation: trigger on SLA KPI breach → Teams notification to supervisor with case link and customer tier
Supervisor real-time dashboard: "Longest Wait" column — supervisors see queue depth and waiting time, can manually assign

Reactive (when it happens):

Supervisor opens case from dashboard → assigns directly to available agent
Or: supervisor uses "Assign" from queue view to push to specific agent
Post-incident: review routing rules and agent capacity allocation for the queue

Scenario: How do you implement seamless chat-to-voice escalation in Omnichannel?

Requirement: Customer on live chat → issue is complex → needs a phone call without losing chat context.

Agent initiates: in chat session → clicks "Consult/Transfer" → selects Voice → enters customer's phone number
D365 initiates outbound call via Azure Communication Services
Multisession merge: voice opens in a new tab. Original chat transcript remains visible alongside.
Context preserved: agent has full chat history during the voice call — customer never repeats
Single case record: both chat and voice activities linked to the same case — unified timeline
Transfer to specialist: if escalating further, all context (chat transcript + call notes) transfers with the conversation

Key value: customer never repeats themselves. Context travels with the conversation across channel escalations.

Scenario: How do you measure and improve First Contact Resolution (FCR) rate?

Measuring FCR in D365:

FCR = cases resolved in first contact without re-open

Power BI calculation:
FCR = (Cases resolved without follow-up) / (Total resolved cases) × 100

Track in D365:
→ Cases with no follow-up case linked (no re-open)
→ Cases where resolvedon = first contact date
→ Monitor re-opened cases (cases resolved then re-activated)

Improving FCR:

Knowledge base quality: Knowledge Analytics → find articles rated unhelpful or linked to re-opened cases → improve or replace
Copilot for agents: AI-suggested responses and case summaries reduce resolution errors that cause re-opens
Skills-based routing: route complex issues to specialist agents first time — avoid unnecessary tier 1 escalations
Customer Service Insights: identify topics with worst FCR rates → target for KB article creation or agent training
Root cause tracking: add "Reason for re-open" field on re-opened cases → analyse patterns (wrong resolution, incomplete fix)

Scenario: How do you configure D365 Customer Service to handle a sudden spike in cases during a product outage?

Increase agent capacity: temporarily raise agent capacity units during the spike — allows agents to handle more simultaneous conversations
Deploy Copilot Studio bot: configure a bot to handle the most common outage-related queries (status updates, workarounds) — deflect volume from live agents
Create outage knowledge article: publish immediately with known issue, workaround, and estimated resolution time — agents share this rather than typing individual responses
Bulk case creation: if customers are proactively notified, pre-create cases for affected accounts with status "Researching" — no customer needs to call
Copilot case summary: agents use Copilot to rapidly understand incoming cases and apply the known resolution faster
Supervisor dashboard: monitor queue depths and agent sentiment — intervene early before queues back up significantly
Post-incident: Customer Service Insights will cluster outage cases into a topic — use for retrospective analysis and knowledge base improvement

10. Cheat Sheet — Quick Reference

Case Status Quick Reference

statecode (Status):
0 = Active    1 = Resolved    2 = Cancelled

statuscode (Status Reason) — Active:
1 = In Progress    2 = On Hold    3 = Waiting for Details    4 = Researching

statuscode (Status Reason) — Resolved:
5 = Problem Solved    1000 = Information Provided    6 = Cancelled

SLA behaviour:
→ SLA starts: on case creation
→ SLA pauses: when statuscode = 'On Hold' or 'Waiting for Details'
→ SLA resumes: when statuscode returns to 'In Progress'
→ SLA stops: when statecode = Resolved or Cancelled

Unified Routing Quick Reference

Components:
Workstream → defines channel + routing mode (push/pick)
Routing rules → classify and assign to queues
Queue → holds work items
Assignment method → how agents are selected from queue

Assignment methods:
Highest capacity → most available capacity units
Round robin      → even distribution
Least active     → fewest active sessions
Skills-based     → skill + proficiency match

Skill relaxation:
After X minutes: lower required proficiency
After Y minutes: accept any available agent in queue

SLA vs Entitlement

SLA (Service Level Agreement):
→ WHAT response/resolution time is committed
→ Defines KPIs, warning thresholds, breach actions
→ Linked to: Entitlement or applied globally
→ Timers shown on: case form

Entitlement:
→ HOW MANY cases/hours a customer is entitled to
→ Tracks remaining support terms
→ Defines: channels available, associated SLA
→ Linked to: Account or Contact
→ Consumed when: case is created

They work TOGETHER:
Entitlement → defines TERMS + specifies which SLA
SLA → defines the TIME commitments for those terms

Omnichannel Channel Architecture

Customer channels:
Website      → Live Chat widget → Chat workstream → Queue → Agent
Phone        → ACS PSTN → Voice workstream → Queue → Agent
SMS          → ACS/TeleSign → SMS workstream → Queue → Agent
WhatsApp     → WhatsApp Business API → Messaging workstream → Queue → Agent
Facebook     → Facebook App → Social workstream → Queue → Agent
Custom       → Direct Line API → Custom workstream → Queue → Agent

All conversations surface in:
→ Customer Service workspace (agent side)
→ Omnichannel Supervisor Dashboard (supervisor side)

Context passed with every conversation:
→ Customer identity (if authenticated)
→ Bot transcript (if escalated from bot)
→ Pre-chat survey responses
→ Routing context variables

Key KPIs Reference

CSAT  = Customer Satisfaction Score
        (post-interaction survey, scale 1–5 or 1–10)

FCR   = First Contact Resolution Rate
        (resolved in first contact / total cases × 100)

AHT   = Average Handling Time
        (total agent time: hold + talk + wrap-up)

ASA   = Average Speed of Answer
        (queue arrival → agent pick-up time)

ABN   = Abandon Rate
        (customers who left queue before answered / total arrivals × 100)

SLA%  = SLA Compliance Rate
        (cases resolved within SLA / total cases × 100)

Deflection Rate = cases resolved by bot / total contacts × 100

NPS   = Net Promoter Score (would you recommend? 0-10)

Top 10 Tips

Case = incident table — the central entity in D365 CS. Know its key fields: subject, description, priority (1=High, 2=Normal, 3=Low), status, status reason, customer (polymorphic: Account or Contact), owner, SLA.
Enhanced SLA over Standard — Enhanced SLA supports multiple KPIs, pause/resume, and automatic breach actions. Standard SLA is legacy. Always recommend Enhanced for production.
Unified Routing replaces basic routing — Unified Routing handles both cases (record routing) and Omnichannel conversations in one engine. Know the pipeline: Classification → Route to Queue → Assignment.
Omnichannel add-on is separate — chat, voice, SMS are not in base Customer Service Enterprise licence. Always confirm add-on requirements when asked about Omnichannel architecture.
Bot-to-human handoff with context — the key architecture pattern: Copilot Studio bot handles first contact → escalates to Omnichannel with full conversation context → agent continues seamlessly.
Agent capacity controls concurrency — voice typically consumes 50+ units to prevent multi-channel conflicts. Know how to configure and why.
Skill relaxation prevents queue backup — gradually lower skill proficiency requirements over time to prevent long waits when exact-match agents are busy.
Entitlements connect contracts to service — they auto-associate SLAs to cases and track remaining support terms. Know the allotment types (cases vs hours).
Copilot reduces AHT and improves FCR — the AI capabilities (ask a question, draft response, case summary) are the primary D365 CS differentiators in 2025. Know all five capabilities.
Customer Service Insights = proactive improvement — topic clustering identifies volume drivers automatically. Deflection opportunities guide knowledge base priorities. This is the data-driven continuous improvement story.

Friday, May 1, 2026