How DCG Governs the Microsoft Environment End-to-End

Most licensing advisory ends at the transaction. A contract is signed, licenses are assigned, and the partner moves on. What happens between that moment and the next renewal? The consumption drift, the over-provisioning, and the support cost accumulation are left to IT to manage without a clear point of accountability.

DCG operates differently. When an organization moves its Microsoft licensing to DCG, the relationship does not end at the sale. It is structured around ongoing governance: defined accountability for how the environment is managed, visibility into what is being consumed, and a path to optimization that does not wait for the next contract event.

This guide walks through what that governance model looks like in practice: how licenses get managed, what IT can see and control, how support works, and what changes when the transition happens.

License Provisioning and Assignment

Under DCG, organizations have two options for how the Microsoft environment is managed. Both are available. The right fit depends on how much operational ownership IT wants to retain.

Under either model, DCG maintains defined accountability for license right-sizing. This distinction matters more than it might appear. Under the current Microsoft commercial model, account management is shifting back to Microsoft under MCA-E. The Microsoft account manager who previously served as a point of contact for licensing questions and escalations is no longer the primary governance layer. DCG fills that gap regardless of which model the organization chooses.

The Self-Service Portal

The self-service portal is the operational interface for the Microsoft environment. For organizations in the self-managed model, it is the primary tool for day-to-day licensing administration. For organizations in the DCG-managed model, it is a transparency layer, a live view of what DCG is managing on their behalf.

The portal exists to give IT direct, persistent visibility into the environment. A live view that supports better decisions when they need to be made. For organizations where IT wants to stay operationally close to the environment, it is the primary governance interface. For organizations that have delegated management to DCG, it is the accountability check.

Ongoing Optimization

Governance does not wait for the next renewal. Under DCG, optimization is a continuous process.

License right-sizing

Licenses are monitored against actual usage on an ongoing basis. Over-provisioned users (those assigned licenses they are not actively using) are flagged for review. Underutilized licenses, including legacy assignments that have not been cleaned up, are identified and surfaced. The result is a tighter alignment between what the organization is paying for and what it is using.

Spend overlap identification

The Microsoft environment is not just licenses. Unified Support costs compound as a percentage of total Microsoft spend, running at 8–12% and growing with every license added. For CSP customers, Azure Reservations and Savings Plans carry their own commercial considerations: they lock in pricing for specific products, but only pay off when they map to genuine, sustained usage, so DCG evaluates them carefully before recommending one. DCG monitors overlap and compounding across all of these layers, beyond the licensing line alone

Optimization between renewals

Issues identified through ongoing monitoring do not wait for the next contract event to be addressed. When over-provisioning is identified, it is actioned. When a consumption pattern creates downstream risk, IT is informed. The goal is to prevent renewal problems, not discover them at the table. For IT, the practical effect is that the environment stays cleaner between renewals without requiring IT to run the analysis themselves.

Microsoft Enterprise Support

For organizations that currently carry Microsoft's Unified Support, the cost structure is worth understanding before any transition. Unified Support is priced as a percentage of total Microsoft spend — typically 8–12% — and it compounds automatically as the licensing footprint grows. Every license added increases the support bill, regardless of whether support usage increases.

DCG's Microsoft Enterprise Support is structured differently: it is a fixed-cost service purchased separately, not a percentage of spend. For Procurement and Finance, this creates a support cost line that can be modeled and held stable, rather than one that grows with the Microsoft environment.

The decision about whether to include Microsoft Enterprise Support is separate from the CSP licensing decision. Some organizations will move licensing to DCG and retain or separately procure support. Others will replace Unified Support with DCG's Enterprise Support as part of the transition. Both paths are available and should be evaluated on their own terms.

SOC II Type 2 - What It Means for IT

Governance claims are only useful if they can be verified. Before IT takes DCG's word for how licensing data is handled and managed, it's worth knowing what independent verification actually stands behind that.

DCG holds SOC II Type 2 certification. For IT, understanding what this means, and what it does not mean, matters for how it gets used internally, whether in a security review, a vendor risk assessment, or a conversation with Procurement.

SOC II Type 2 is an independent audit of an organization's internal controls over a defined period of time. It covers how DCG manages security, availability, processing integrity, and confidentiality within its own operations, conducted by a third-party firm over a sustained period.

What this means for IT

DCG's governance controls have been independently verified. The claims made about how the environment is managed, how data is handled, and how the operational model works are not self-attested. They have been audited by an external firm.

What this does not mean

SOC II Type 2 measures DCG's internal controls, not the client's environment. It does not certify the organization's own compliance posture and should not be represented as doing so internally.

How this gets used

For IT teams that need to validate a vendor's governance posture for an internal security or compliance review, SOC II Type 2 documentation is available from DCG. For Procurement teams making the case to IT or legal that DCG is a credible governed partner, it is a verifiable data point.

What Changes Operationally and What Does Not

The most common concern IT has before a licensing model change is disruption. It is worth addressing directly.

What does not change

The Microsoft products IT manages are not affected by a commercial model transition. Microsoft 365, Teams, Azure, and other services continue to operate as they do today. Users do not experience any change to their environment. Provisioning and assignment remain self-service under the self-managed model.

What changes

The commercial relationship (who is accountable for it, who IT contacts for licensing questions, and how the environment is governed between renewals) is what changes. Under DCG, that accountability sits with DCG, not with a Microsoft account manager managing the relationship at a distance, and not with IT absorbing the coordination gap on their own.

The degree of operational change on IT's side depends on the governance model the organization chooses. For organizations that self-manage through the portal, the change is minimal. IT maintains the same hands-on control they have today, with DCG available when they need assistance. For organizations that delegate management to a DCG account executive, IT gains a partner actively managing the environment on their behalf.

In both cases, what IT gains is a clear point of accountability that does not exist in a transactional CSP relationship or in the current Microsoft account management model under MCA-E.

Evaluate a Governed CSP For Your Environment

If the governance model described in this guide is what your organization needs, the next step is understanding what a transition would look like.

DCG's EA-to-CSP Transition Plan documents the migration step by step: what gets assessed, what gets moved, what IT needs to validate, and how the transition is structured to avoid operational disruption. It is designed so IT can review it, raise questions, and sign off on feasibility before anything is committed.

‍