No support being received from microsoft techincal support

Escalate the existing case through the organization that sold the subscription, or use Enhanced Engagements → Service Requests → Nudge if that capability is included in your Microsoft support agreement.

1. Identify the correct escalation owner

Check Microsoft 365 admin center → Billing → Your products and determine how the affected subscription was purchased:

• Purchased entirely through a Microsoft partner/CSP: escalate through that partner. Microsoft states that customers whose subscriptions were all purchased through a partner must contact that partner for support.^1^ Ask the partner to:
  • Escalate the existing Microsoft case through its support agreement.
  • Provide the partner escalation/reference number.
  • Assign an escalation owner and a defined update cadence.
  • Address any immediate renewal or licensing-continuity options available under your agreement.
• Purchased directly from Microsoft: keep the existing case as the primary record and use the applicable route below. Opening duplicate cases can fragment ownership; Microsoft recommends separate requests for separate issues, not multiple requests for the same issue.^1^

2. Use Nudge if your tenant has Enhanced Engagements

If Enhanced Engagements is available under your support entitlement:

1. Open Enhanced engagements → Engagements → Service Requests.
2. Search for the existing ticket number.
3. Open the active request and select Nudge.
4. Select the reason that best represents the business impact.
5. Enter:
   • Number of users and services affected.
   • Financial or operational impact.
   • Whether a workaround exists.
   • Date the impact started.
   • Current licensing/renewal deadline.
   • The specific request: escalation owner, next engineering milestone, mitigation plan, and next-update time.
6. Attach relevant evidence and nominate a primary contact.
7. Select Submit.

Nudge is specifically intended for cases affecting business operations or whose progress is not meeting expectations. Its status progresses through Initiated, Acknowledged, and Actioned; the case view also records follow-up nudges and timestamps.^2^

If Enhanced Engagements is not present, this route is not available under the tenant’s current entitlement.

3. Escalate through the commercial account team

If your company has a Microsoft account manager, Customer Success Account Manager, or support contract manager, send that person the existing case number and request a formal case review. Microsoft’s subscription-issue guidance specifically directs organizations with a dedicated account manager to work with their Microsoft account team.^3^

Use a concise impact statement such as:

Existing case [case number] has been open since [date] for a Microsoft-confirmed product issue affecting license renewal. It currently affects [users/services], has [no workaround/workaround limitations], and creates [operational or financial impact]. Please assign an escalation owner and provide the next engineering milestone, mitigation options, renewal/service-continuity plan, and a scheduled update time.

Do not post the case number, tenant information, invoices, or contact details publicly.

4. If none of those channels is available

Have a Microsoft 365 administrator contact business support and reference the existing case rather than starting the investigation again:

1. Microsoft 365 admin center → Help & support.
2. Select the Contact Support headset icon.
3. Choose phone or email and request review of the existing case by its case number.^1^
4. If calling, use the current regional number listed through Microsoft’s support page. Administrators should have the account details ready. Microsoft may send a verification code to the email address or phone number registered in the admin-center profile when the caller’s number is not registered.^1^

Since ordinary update and management-escalation requests have already produced the same response, make this request concrete: ask for the named escalation owner, assigned severity, engineering escalation status, interim mitigation, service-continuity plan, and next scheduled update. A confirmed bug does not necessarily have a publishable fix date, but the case owner or account team should still manage impact, milestones, and communications.

References

1. Get support for Microsoft 365 for business
2. Engagements in Enhanced Engagements
3. SharePoint service access affected by Microsoft 365 subscription issues