Defined implementation
Take direct control of your Microsoft 365 account.
Move billing, administrator access and support away from GoDaddy through a planned transition that protects email access and existing data. Mail flow is tested on the new path, and anything left over is closed or given an owner.
PricePrice fixed after a short scope call.
DeliveryAllow 5 to 10 business days for planning; provider timing is confirmed separately, with AZ work in agreed windows
What you receive · illustrative sample
The client keeps control and the handover record.
Illustrative tenant ownership checklist. A provider release and a data migration are different scopes.
| Control | What is verified | Handover |
|---|---|---|
| Administration | Authorized client administrator can sign in | Access record |
| Mail and licenses | Mail-flow tests and license assignment checks | Validation sheet |
| Ownership | Domain, billing and provider responsibilities agreed | Owner register |
Related delivery record
Provider exit: administrative control and messaging continuity
Read what changed and how it was checked ↗Engagement context
When this engagement applies.
Microsoft 365 was bought through GoDaddy, and billing, admin control, or licensing is now blocked by it.
Scope considerations
- One GoDaddy-managed Microsoft 365 tenant
- Administrative cooperation and access available
- Client owns user communications
The defined work
Engagement scope.
- 01
Administrative access, domains, mailboxes, licensing and mail-routing add-ons are inventoried before release.
- 02
The license plan and payment route are prepared; purchase and assignment follow GoDaddy’s documented release sequence in the existing tenant.
- 03
The provider-led release is coordinated through GoDaddy; AZ work is scheduled around confirmed readiness.
- 04
Mail flow, sign-in, administrator ownership and the starting inventory are checked after the change.
Acceptance
Completion has an agreed standard.
Done when direct administrative control and licensing are confirmed, sign-in and mail flow pass, and every starting mailbox and domain is accounted for.
The tenant is under direct Microsoft or CSP billing
Mail sends and receives on the new path, tested
Every mailbox and domain is checked against the list you started from, and anything left over is closed or has a named owner
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 domains
- Whether licensing has to be re-purchased directly from Microsoft or a CSP
- Number of mailboxes to verify after the move
Delivery calendar
Allow 5 to 10 business days for planning; provider timing is confirmed separately, with AZ work in agreed windows
How engagements workScope & responsibilities
The full engagement boundary.
Review the exclusions, required client participation, change controls and operational handover for this engagement.
Exclusions
- Microsoft licensing costs
- Mailbox or file migration beyond the defederation itself
- Help desk and end-user support
Client responsibilities
- Provide a payment method or CSP relationship for direct Microsoft billing
- Approve the cutover window
- Own end-user communications
Change and rollback method
- The starting tenant, domain, mailbox and mail-route state is captured before release.
- Access and the licensing sequence are checked before release. New licenses are purchased at the documented stage after the provider move, in the existing tenant.
- The release is stopped if ownership, licensing or mail-route prerequisites do not pass the pre-check.
Operational record and handover
- Tenant and domain inventory before and after
- Administrator ownership and licensing confirmation
- Sign-in and mail-flow test results
- Handover record with every remaining item assigned
Related delivered work
GoDaddy defederation and migration, delivered five times
Five completed GoDaddy exits sit on the delivered-engagement record, each ending in direct control, tested mail flow, and a tenant checked against the original list.
Read selected workBefore 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 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.
Plan the GoDaddy Exit