The scoping letter is the most consequential artefact in a Microsoft SAM engagement: the legal entities, the products, the deployment estates and the time windows that follow. The Admodum read on the perimeter contest and the language that closes the scope.
The legal-entity perimeter is the first scope to contest. The publisher's first draft typically reads "the customer and its affiliates" without further specification; the active enrolment, by contrast, names a specific parent legal entity and a specific list of authorised affiliates, and only those entities sit inside the enrolment.
The buyer-side discipline is to read the enrolment's Authorised Affiliate appendix, list the entities that are inside the perimeter, list the entities that are outside the perimeter (divested business units, separate-enrolment subsidiaries, recent acquisitions running on Cloud Solution Provider tenants, contractor-only populations on a CSP tenant, joint-venture entities, statutory subsidiaries not enrolled), and put both lists into the scoping letter as the agreed perimeter.
The wider engagement reference is at the SAM audit anatomy spoke; the renewal cadence sits at Microsoft EA renewal cycle; the wider editorial sits in the Microsoft pillar.
The product perimeter narrows to the products on the active enrolment. The buyer holds the enrolment's price-sheet appendix and the order-form history; only products on that appendix or order-form are inside scope. Everything else is excluded by explicit list.
Common over-reach to contest: free SKUs (Power BI Free, Teams Free, M365 Apps for Business on personal subscriptions) that are not enrolment products; evaluation versions installed for sixty- or ninety-day trials; MSDN / Visual Studio Subscription entitlements covered by separate per-user terms; Defender for Cloud and Microsoft 365 Apps for Business that have separate consumption mechanics; embedded OEM Windows installs on contractor-supplied devices that carry their own OEM licence.
The wider product context sits at the M365 plans spoke; the per-product per-host context for Windows Server and SQL Server sits at Windows Server core licensing and SQL Server licensing.
The deployment-estate perimeter narrows to the estates the publisher has the contractual right to read. The on-prem estate inside the named legal entities sits inside the perimeter; the Azure tenant the customer owns sits inside the perimeter; CSP tenants run by other organisations on behalf of the customer (managed-service-provider tenants, distributor tenants) sit outside the perimeter because the customer is not the tenant of record.
Multi-cloud is the most common contest. Workloads running Microsoft software on AWS or Google Cloud under license-mobility entitlements are read against the underlying licence, not against the hosting cloud; the SAM partner's natural reach is into the on-prem and Azure estates only.
The user-population perimeter narrows to the user populations covered by the enrolment. The buyer-side discipline is to map every user-licensed product to its qualifying population: employees of the named legal entities are inside, contractors on the customer's directory under documented contract terms are inside, contractors managed by a managed-service provider on their own tenant are outside, customers and external collaborators on B2B guest invitations are outside (guest seats have separate licensing rules).
Recent acquisitions that have not yet been added to the Authorised Affiliate appendix sit outside the perimeter; the SAM partner's natural reach is to include them, the buyer-side discipline is to exclude them until the next True-Up reads them in.
The wider seat-assignment hygiene sits at the seat-assignment hygiene spoke; the per-user per-device construct sits at per-user versus per-device; the frontline construct sits at M365 frontline plans.
The time-window perimeter is the most consequential and the most contested. The publisher's first draft is often unbounded ("the customer's deployment as at the date of scan"), which permits look-back into deployments that pre-date the active enrolment. The buyer-side discipline is to bound the look-back to the current enrolment year and, where the enrolment terms specify a True-Up review window, to the prior enrolment year.
The Volume Licensing terms grant the publisher an audit right "during the term of this agreement and for one year thereafter", which sets the contractual ceiling; anything older sits outside the perimeter. The MCA-E equivalent (see MCA-E versus the Enterprise Agreement) carries its own audit-clause language.
The wider true-up cadence sits at EA True-Up mechanics; the renewal cadence sits at microsoft EA renewal cycle; the negotiation calendar sits at the Microsoft fiscal year.
At the close of scoping, the buyer holds five artefacts: the agreed scoping letter (with explicit included and excluded lists for each of the five perimeters), the read of the Authorised Affiliate appendix (with the named entities inside and the named entities outside), the read of the enrolment price-sheet (with the named products inside and the excluded SKUs outside), the read of the deployment-estate inventory (with the on-prem and Azure tenants named and the multi-cloud and CSP tenants explicitly out of scope), and the read of the audit-window clause (with the current and prior enrolment years named).
The settlement posture that follows is shaped at scope. The wider settlement context sits at the SAM settlement position spoke; the engagement-models read sits at the Fixed Fee, Contingency and Annual Retainer pages; the practice sits at Microsoft; the aggregated reading list sits at the Microsoft knowledge hub; active audit moments route to Audit Defence; renewal moments route to the Renewal Programme.
A senior Admodum Microsoft advisor will read your scoping letter, the Authorised Affiliate appendix and the audit-clause language against the perimeter discipline on a private call. Active audit moments route to Audit Defence.