Request an Architecture Briefing

Defined implementation

Stop paying for Microsoft licenses nobody uses.

License assignments are corrected where you authorize it. Every line gets a cancel, change or keep decision. Finance receives a renewal cost model built from what people actually use.

PricePrice fixed after a short scope call.

DeliveryThe deadline is your Microsoft renewal date, which your agreement already fixes. The delivery calendar is confirmed against it before anything is signed.

Fix the Renewal Review scope & terms

What you receive · illustrative sample

A review should leave you with a decision.

Illustrative findings record. Defined follow-on work can be quoted; unresolved dependencies carry assumptions and estimates.

FindingDecision neededWhat you receive
Unclear system ownershipConfirm accountable ownerOwner/dependency register
Renewal or capacity choiceCompare equivalent optionsDated assumptions and cost basis
Priority correctionAgree scope and acceptancePlan with responsibilities and next steps

Meet the person responsible for delivery.

Alwatheq Zboun leads the agreed work. A sample shows the format; the statement of work defines your deliverable and acceptance checks.

Engagement context

When this engagement applies.

A Microsoft renewal or true-up is coming. Microsoft’s July 1, 2026 price and packaging change lands when you renew, not today.

Related source documentation

Microsoft: commercial price and packaging update

Scope considerations

  • Tenant-side changes only
  • Commercial actions stay with you or your reseller
  • Timed to land before the renewal date

The defined work

Engagement scope.

  1. 01

    Licenses are checked against who actually signs in: who holds one, who has not used it, and who is on a bigger plan than their work needs.

  2. 02

    Where authorized, tenant-side assignments are corrected — released, downgraded, or reassigned — rather than described in a document for someone else to action.

  3. 03

    Duplicate add-ons and capabilities already bundled in an owned plan are identified and the overlap is removed.

  4. 04

    The renewal cost model is built: current spend, corrected spend, and the delta each decision is worth.

  5. 05

    The commercial actions that only a buyer or reseller can take — CSP quantity changes, EA true-up positions — are written up and assigned by name.

Acceptance

Completion has an agreed standard.

  • Every license line carries a keep, downgrade, consolidate or cancel call with the reason recorded

  • Authorized assignment changes are made in the tenant and verified

  • The target assignment matrix is confirmed and signed off

  • Finance has the current-versus-renewal cost model

  • Every commercial action is assigned to a named person on the buyer or reseller side

Commercial basis

Price, scope and timing are considered together.

Engagement price

Price fixed after a short scope call.

The price is agreed in writing before any work starts and before anyone is given access. The call itself costs nothing. What moves the number:

What determines the scope

  • Number of license lines and distinct subscriptions
  • Number of tenants
  • Whether the cost model is handed over as a document or built as a refreshing dashboard in your own workspace
  • Whether assignment changes are executed by AZ or handed over as a target matrix
  • Whether the agreement is CSP, EA, or direct
  • How far ahead of the renewal date the work starts

Delivery calendar

The deadline is your Microsoft renewal date, which your agreement already fixes. The delivery calendar is confirmed against it before anything is signed.

How engagements work

Scope & responsibilities

The full engagement boundary.

Review the exclusions, required client participation, change controls and operational handover for this engagement.

Exclusions
  • Placing, cancelling or negotiating any order with Microsoft or a reseller
  • Any guarantee of a specific saving, which depends on decisions that are not AZ’s to make
  • Contract or legal review
  • Third-party software licensing outside Microsoft 365 and Azure
Client responsibilities
  • Confirm which assignment changes are authorized before any are made
  • Provide the current agreement, quantities and renewal date
  • Name the person who will execute the commercial actions with the reseller or Microsoft
  • Confirm leavers and role changes the tenant does not know about
Change and rollback method
  • Nothing is removed on the basis of a report alone: every assignment change is confirmed against sign-in evidence and authorized in writing first.
  • Changes run in batches with a hold period, so a wrongly released license is caught and restored within the retention window rather than after it.
Operational record and handover
  • The license position, line by line, with the waste named in dollars
  • The sign-in evidence behind every release or downgrade
  • The target assignment matrix, as agreed
  • The current-versus-renewal cost model
  • The list of commercial actions, each with a named owner and a date

Before you commit

A clear first step.
You stay in control.

Start with the problem and the result you need. The initial fit conversation is free and does not require access to your systems.

Check client feedback on Upwork ↗

Prefer to contract through Upwork? Contact Alwatheq there. Existing Upwork engagements continue through Upwork.

Who will actually do the work?

Alwatheq Zboun leads the scope, technical work and handover. If a specialist collaborator is needed, their role is agreed with you before work starts. Your proposal names the responsibilities and delivery windows.

What happens before you get access?

We agree the scope, fee and completion checks in writing. Access uses named accounts and only the permissions the work requires. Approved access is reviewed and removed at handover.

How do we know the change worked?

Your scope defines the pilot, test cases and acceptance checks. Results and exceptions are recorded. Recovery options and their limits are agreed before production changes; a failed check is addressed before the next approved stage.

Will we need an ongoing retainer?

A defined project can end at handover. Your team receives the agreed configuration records, runbook and walkthrough. Any limited support period is written into the proposal; ongoing support or additional work is a separate agreement.

Discuss the fit ↗Read the delivery process ↗

Discuss this engagement

Put the scope in context.

Describe the problem, systems and deadline. Alwatheq will review the fit and the scope questions before preparing a written proposal.

Fix the Renewal