Microsoft Dynamics 365 Business Central cloud support operates across three distinct layers: Microsoft’s managed infrastructure, your implementation partner’s configuration and extension ownership, and your internal platform team’s tenant-level responsibilities. Understanding where each layer begins and ends is what separates a team that resolves incidents quickly from one that spends hours routing tickets to the wrong owner.
This article covers escalation paths, connected data troubleshooting, Teams integration support, update management, and the diagnostic tools your team should have running before the next incident occurs.
- Microsoft does not provide direct end-user support for Business Central — your Cloud Solution Provider (CSP) partner is the first escalation point for most issues.
- Microsoft owns platform availability, core application bugs, and Azure infrastructure. Your partner owns extensions, configurations, and business process support.
- Most Business Central connectivity failures with Microsoft 365 services originate in Microsoft Entra ID permission misconfigurations, not in Business Central itself.
- Microsoft releases two major Business Central updates per year. Platform teams can schedule the update window but cannot skip updates entirely.
- The Business Central admin center and Azure Application Insights are your primary tools for monitoring, diagnostics, and update scheduling.
How Business Central Cloud Support Is Structured
Business Central online runs on Microsoft Azure as a fully managed Software as a Service (SaaS) platform. Microsoft handles the underlying infrastructure, platform availability, and core application updates. Your platform team does not manage servers, databases, or runtime environments directly. That said, moving infrastructure responsibility to Microsoft doesn’t eliminate your team’s obligations — it shifts them.
Support responsibility divides across three layers. Microsoft covers the platform. Your CSP partner or implementation partner covers customizations, extensions, and configuration. Your internal team covers tenant administration, user permissions, integration configuration, and update scheduling. When an incident occurs, the first question your team should answer is: which layer does this issue belong to?
Building a documented escalation matrix before an incident happens is the most practical step your team can take. Map issue types (extension bugs, API failures, environment health, user access errors) to the correct resolution owner. Without that map, incidents generate confusion rather than resolution.
Microsoft’s Support Tiers for Business Central Online
Microsoft offers tiered support plans for Dynamics 365 Business Central. Each tier carries different response time SLAs and escalation access. Platform teams should know which plan their organization holds before an incident forces the question.
- Developer Support: Self-service resources, documentation, and community forums. No direct Microsoft engineer access. Appropriate for non-production environments and development work.
- Standard Support: Includes access to Microsoft support engineers for break-fix issues. Response times vary by severity. Covers cloud service incidents.
- Professional Direct: Faster response SLAs and proactive advisory support. Includes access to a designated support team for Dynamics 365 workloads.
- Unified Support: Microsoft’s highest-tier offering, replacing Premier Support. Provides the fastest response times, a designated Customer Success Account Manager, and direct escalation paths for severity A production outages.
Business Central online customers access Microsoft support through the Microsoft 365 admin center or the Power Platform admin center, not through a separate portal. For critical production outages, severity A escalation requires your team to document business impact clearly and submit through the admin center. Know your support tier and your escalation path now, not when a production environment goes down.
Partner vs. Microsoft: Who Resolves What
This boundary causes more support delays than almost anything else. Microsoft does not troubleshoot partner-built extensions, custom configurations, or business process issues. If your Business Central environment includes per-tenant extensions (code your partner developed and deployed), Microsoft will direct you back to that partner for any issue touching that code.
What Microsoft Owns
- Platform availability and Azure infrastructure health
- Core application bugs in the base Business Central product
- Security vulnerabilities in Microsoft-managed components
- Major and minor update delivery
What Your Partner Owns
- Extension conflicts and custom code bugs
- Configuration errors introduced during implementation
- Business process support and workflow issues
- Integration setup between Business Central and third-party systems
Your internal team sits between these two. You own tenant administration, user access management through Microsoft Entra ID (formerly Azure Active Directory), update scheduling, and first-level triage before routing to a partner or Microsoft. Build your escalation matrix around these ownership lines, and share it with your partner during your next quarterly review meeting.
Troubleshooting Connected Data Issues with Microsoft 365
Business Central integrates with Outlook, Excel, and Microsoft Teams through Microsoft Graph API connections. When synchronization fails, the failure point is often not Business Central itself. Most connectivity errors originate upstream, in permission configurations or token management.
How to Troubleshoot Business Central Cloud Connectivity Issues
- Check Microsoft Entra ID app registrations. Verify that the Business Central service principal has the correct API permissions assigned and that admin consent has been granted at the tenant level.
- Verify OAuth token status. Expired or revoked tokens are a common cause of silent sync failures between Business Central and Microsoft 365 services.
- Review delegated permissions. Missing delegated permissions on the Graph API connection block service-to-service calls without generating obvious error messages in Business Central.
- Check conditional access policies. Tenant-level conditional access policies in Microsoft Entra ID can block service-to-service authentication without any alert in the Business Central interface.
- Open the Business Central admin center. Review environment health status and active incidents before escalating to your partner.
- Contact your partner or Microsoft. If the issue persists after checking permissions and token status, route to your partner for extension-level review or to Microsoft if the failure points to core platform behavior.
Microsoft Teams Integration: Support Responsibilities
The Business Central app for Microsoft Teams allows users to share and view Business Central records directly inside Teams conversations. This integration runs through the Microsoft Teams app framework and Microsoft Graph, not a custom connector your team built. That architecture matters when something breaks.
When the Teams integration fails, the issue can sit in three places: Teams app deployment policies, Business Central environment permissions, or the Microsoft Graph connection. Each has a different resolution path. Start by verifying Teams app deployment policies in the Microsoft Teams admin center. Confirm that the Business Central app is deployed to the correct user groups and that app permission policies allow it to run.
If app deployment looks correct, check Business Central environment permissions to confirm the affected users have the right access roles assigned. If both checks pass and the integration still fails, the issue likely sits in the Graph API connection, which routes back to Entra ID permissions.
Managing Business Central’s Mandatory Update Cadence
Microsoft releases two major updates per year for Business Central online: Wave 1 in spring (generally April) and Wave 2 in fall (generally October). Monthly minor updates ship between major waves. Your team cannot opt out of updates, but you can schedule when the update applies to your production environment within Microsoft’s defined window.
| Release Wave | General Availability | Preview Window | Mandatory Cutoff | Platform Team Actions |
|---|---|---|---|---|
| Wave 1 | April | February–March | June | Test extensions in sandbox, schedule production update, communicate to stakeholders |
| Wave 2 | October | August–September | December | Test extensions in sandbox, schedule production update, communicate to stakeholders |
If your team doesn’t schedule the update within Microsoft’s allowed window, Microsoft applies it automatically. Treat update scheduling as a recurring operational task. Major updates require testing extensions and customizations in a sandbox environment before the update reaches production. Coordinate with your partner on extension compatibility during the preview window, not after the mandatory cutoff. Subscribe to the Microsoft Dynamics 365 Business Central release plan page to receive proactive notifications about upcoming feature changes that may affect your environment.
Monitoring and Diagnostic Tools for Platform Teams
The Business Central admin center is your primary operational dashboard. It provides environment health status, update scheduling controls, and telemetry configuration. If your team isn’t checking it regularly, you’re managing the platform reactively instead of proactively.
Azure Application Insights integration allows your team to stream Business Central telemetry data for performance monitoring, error tracking, and usage analysis. Configuring this connection gives you visibility into query performance, failed operations, and integration errors before they escalate into support tickets. The Business Central performance toolkit, built on Microsoft’s AL language, gives development-oriented platform members tools to diagnose extension-level performance issues independently.
What Platform Teams Should Do Next
Business Central cloud support works well when your team has clear ownership boundaries, a documented escalation matrix, and the right monitoring tools running before an incident occurs. The three-layer model — Microsoft, partner, internal team — gives you a structure. The work is filling in that structure with specific contacts, issue type mappings, and operational workflows your team can act on under pressure.
- Confirm your organization’s Microsoft support plan tier and document the escalation path for severity A incidents.
- Map issue types to resolution owners — Microsoft, your CSP partner, and internal IT — in a single reference document.
- Configure Azure Application Insights telemetry for your Business Central environment.
- Schedule a quarterly support review with your partner to align on open tickets and upcoming release wave impacts.
- Contact PaasLane to discuss a cloud platform assessment if your team is unsure whether your current support structure and escalation paths are optimized for Business Central in the cloud.
Frequently Asked Questions
Who is responsible for Business Central updates in the cloud?
Microsoft delivers and applies all major and minor updates to Business Central online. Your platform team is responsible for scheduling when the update applies to your production environment within Microsoft’s defined window, and for testing extensions in a sandbox environment before the update goes live.
What happens when my Business Central integration with Teams stops working?
Start by checking Teams app deployment policies in the Microsoft Teams admin center, then verify Business Central environment permissions for affected users. If both look correct, the issue likely sits in the Microsoft Graph API connection and traces back to Entra ID permissions. Each failure point has a different resolution path.
How do I escalate a Business Central issue to Microsoft directly?
Access Microsoft support through the Microsoft 365 admin center or the Power Platform admin center. For critical production outages, submit a severity A ticket and document the business impact clearly. Your support plan tier determines response time SLAs and the level of Microsoft engineer access you receive.
What is the difference between a CSP partner and Microsoft direct support for Business Central?
A CSP partner handles configuration issues, extension bugs, and business process support — areas Microsoft doesn’t cover directly. Microsoft direct support covers platform availability, core application bugs, and Azure infrastructure issues. Most Business Central customers route first-level support through their CSP partner, with Microsoft direct support reserved for platform-level incidents.
