Resources

10.09.2026

12 Clear Signs Your Managed Services Relationship Is Not Working

Back to all articles

A Dynamics 365 environment can remain technically available while the managed services relationship around it is failing. Users build workarounds, improvement work stalls, key knowledge concentrates in one person, and internal teams spend more time managing the provider. Recognizing the pattern early gives you a chance to repair the relationship or change it before risk and frustration grow.

Why an underperforming service can be difficult to recognize

One major outage is visible. A gradual decline is not. Slow erosion often appears as many small compromises: a recurring problem is worked around again, an update is postponed, an enhancement has no clear owner, or a user chooses a spreadsheet because requesting a change feels too difficult.

Traditional service reporting can hide that deterioration. A provider may meet an initial-response target while restoration takes too long. Ticket volumes may fall because users have stopped reporting issues. A backlog may appear stable only because old requests are closed without delivering the intended outcome.

Relationship health should therefore be judged across four dimensions:

  • Reliability: Are critical processes stable, and is recurring demand decreasing?
  • Transparency: Can both sides see priorities, ownership, capacity, risks, and decisions?
  • Capability: Can the provider support the connected Microsoft platform and the processes that depend on it?
  • Progress: Is the service helping the organization adopt releases, remove friction, and improve outcomes?

Twelve warning signs that deserve attention

1. The same issues keep returning

Tickets are closed, but underlying causes are not investigated or preventive actions never reach the roadmap. Recurrence may point to configuration, integration, data quality, process design, training, or monitoring. Treating each occurrence as a separate incident creates activity without improvement.

2. The service is almost entirely reactive

All available time is consumed by tickets. There is no protected capacity for release readiness, environment health, security reviews, technical debt, optimization, or adoption. The system may appear stable today while future risk quietly accumulates.

3. The backlog is opaque

You cannot see status, ownership, age, dependencies, estimates, blockers, or why priorities changed. Important requests move forward through escalation or personal relationships rather than a visible governance process.

4. Communication happens only when you chase

Updates repeat that an issue is “in progress” without explaining what has been established, what happens next, who owns the action, or when another update will arrive. Internal teams become the service coordinator instead of the customer.

5. Service levels look healthy while users remain frustrated

Reporting emphasizes initial response and ticket closure, but ignores time to restore service, quality of resolution, recurrence, backlog age, or business impact. The measures may be contractually correct while failing to represent the experience.

6. The relationship depends on one consultant

Work stalls when that person is unavailable. Other team members repeatedly request the same context, and the customer hesitates to escalate because losing the consultant would feel dangerous. This is a continuity risk, even when the individual is excellent.

7. Important knowledge is not documented

Configuration decisions, integrations, deployment procedures, known errors, security arrangements, and operational routines live in email threads, tickets, or individual memory. The longer this continues, the harder and more expensive any future transition becomes.

8. Microsoft releases repeatedly create surprises

Impact assessment, testing, and business communication begin too late. Deprecated features, changes in behaviour, or new opportunities are discovered close to production deadlines. Release management has become an emergency rather than a routine discipline.

9. Enhancements reproduce legacy complexity

The partner implements requests without challenging whether standard functionality, configuration, process change, or a simpler design would be better. Customization grows, future updates become harder, and old ways of working are recreated in a modern platform.

10. No one owns the connected platform

Dynamics 365, Power Platform, Fabric, Azure, and Microsoft 365 issues are passed between teams. Each provider addresses its component, but no one follows the problem through the complete business process or takes responsibility for coordination.

11. Security and access practices are unclear

Privileged access, environment changes, deployments, service accounts, and consultant onboarding or offboarding lack visible control. Requests for evidence produce incomplete answers. This is more than a service-quality concern; it can become a governance and audit risk.

12. There is no credible improvement story

After a year, the same friction remains. Support demand has not reduced, the platform roadmap is disconnected from business priorities, adoption is weak, and governance meetings review activity without making decisions.

The most serious sign is loss of trust. When business teams stop raising issues because they expect delay or poor answers, ticket volumes may fall while operational risk rises.

Measure the pattern and its business impact

One difficult month or one major incident does not necessarily justify changing providers. Review six to twelve months of evidence so the decision reflects a sustained pattern.

Useful evidence includes:

  • Recurring incidents and repeated workarounds.
  • Time to restore critical processes, not only initial response time.
  • Backlog age, blocked requests, missed commitments, and reopened tickets.
  • Release assessments, testing outcomes, and production issues after updates.
  • Enhancement throughput and whether promised benefits were realized.
  • Documentation gaps and reliance on specific individuals.
  • User and process-owner feedback.
  • Internal time spent chasing updates, coordinating suppliers, or correcting provider work.
  • Security, access, or change-control exceptions.

Connect those findings to consequences the business understands: delayed close, interrupted order processing, billing errors, manual effort, control gaps, missed customer commitments, slower decisions, or inability to adopt useful functionality.

Also examine the customer side of the operating model. A new provider cannot indefinitely compensate for unclear priorities, unavailable process owners, delayed decisions, uncontrolled internal changes, or insufficient capacity.

Decide whether to repair the relationship or replace the partner

Clarify what is failing

Compare actual performance with the agreed service. Some problems represent failure to deliver commitments. Others reveal that the contract no longer matches the environment. A break-fix agreement, for example, cannot reasonably deliver a large optimization roadmap without additional capacity.

Separate four possible causes: provider performance, an unsuitable service design, weak shared governance, and unmet customer responsibilities. More than one may be present.

Use a time-bound recovery plan

If the relationship is repairable, agree specific actions, owners, measures, and review dates. The plan might include a new service lead, a backlog reset, root-cause reviews, documentation recovery, revised governance, protected proactive capacity, or specialist involvement.

Meaningful behavioural change should normally be visible within one or two governance cycles. Complex technical improvements may take longer, but ownership, transparency, and communication can improve immediately.

Changing partner is justified when:

  • Material commitments are repeatedly missed without credible corrective action.
  • The provider cannot supply the expertise or capacity the environment requires.
  • Security, access, change, or documentation practices create unacceptable risk.
  • Leadership remains defensive or opaque when concerns are raised.
  • Key-person dependency persists despite repeated requests for continuity.
  • The service model is fundamentally misaligned and the provider cannot adapt it.
  • Trust has deteriorated to the point that teams avoid collaboration or withhold information.

Changing providers is a risk decision, not a punishment. Remaining with a structurally weak service also carries risk: disruption, technical debt, stalled improvements, and dependency that becomes harder to unwind.

How to change partners without creating new disruption

Treat the transition as a focused transformation program. It needs scope, ownership, discovery, knowledge transfer, access control, acceptance criteria, and a stabilization period.

  • Define the future service. Document applications, integrations, critical processes, coverage, service levels, governance, specialist needs, current risks, and planned initiatives.
  • Protect continuity. Identify critical business periods, open incidents, upcoming releases, expiring certificates, scheduled jobs, integrations, and changes in flight.
  • Secure ownership of assets. Confirm that the organization controls source code, solution files, documentation, credentials, licenses, environments, repositories, vendor contacts, and service records.
  • Plan structured knowledge transfer. Organize sessions around architecture and end-to-end processes instead of an unstructured review of old tickets.
  • Review access. Grant the incoming provider least-privilege access through approved identities. Remove outgoing access at the agreed point and retain appropriate audit evidence.
  • Reset the backlog. Separate urgent stabilization, known issues, technical debt, enhancements, and longer-term opportunities.
  • Validate critical operations. Let the new provider observe key cycles, verify monitoring, and rehearse escalation before responsibility transfers.
  • Set 30-, 60-, and 90-day measures. Evaluate ownership, communication, knowledge coverage, backlog clarity, and risk reduction — not only ticket closure.

A successful transition should leave the organization with clearer ownership and better information than it had before. Simply transferring the old operating model to a new supplier will reproduce many of the same problems, so make sure your incoming partner receives extensive information to get up and running smoothly. Here are some things that are critical to share with the new partner: solution architecture, integrations catalogue, customizations performed, security model, critical processes and escalation contacts.

Turn support concerns into a clear decision

D6 Global can assess the current service model, stabilize priority risks, and establish a transparent support and continuous-improvement approach across your Microsoft platform.

Ready to transform your business?

We'd love to hear from you - send us a message and we'll be in touch soon.

General contact

Partnerships

First Name*
Last Name*
Organization Name*
Email*
Job Title*
Department*
Message