Need to open a Microsoft support ticket for Dynamics 365, Power Automate, Power BI, or Power Apps? Here is the current way to do it, from the Power Platform admin center.
You need a valid support plan to open a request. If you do not have one, Microsoft prompts you to add support or points you to self-help options.
How to create the support request
- Sign in to the Power Platform admin center at admin.powerplatform.microsoft.com.
- In the left-hand navigation, select Support, then Support requests, then Get support.
- Use the support agent to describe the issue and create a support request.
- Describe your issue. Microsoft's intake uses an AI agent that reads your description, predicts the product, and may ask clarifying questions. Add as much detail as you can so it routes correctly.
- Confirm the predicted product is right. If it is wrong, select No and choose the correct product (Dynamics 365, Power Automate, Power BI, or Power Apps).
- Pick the problem type closest to your issue, and select the environment if asked.
- Work through the remaining prompts and submit the ticket.
That is it. You can track the request from the same Support area.
RELATED: What Is Microsoft Power Automate?
Tip: give the agent everything up front
The more detail you provide (exact error text, when it started, which environment, steps to reproduce), the faster Microsoft can route and resolve the ticket. Vague descriptions get bounced back with clarifying questions and slow everything down.
If you would rather not manage Microsoft tickets yourself, a partner can handle support, environment management, and escalations for you. Our Dynamics 365 and Power Platform team does exactly that as part of managed services.
What to include in the ticket
A good support ticket gives Microsoft enough context to route the issue without several follow-up questions. Include the affected product, environment name, region, user impact, error message, screenshots if available, when the issue started, and the exact steps that reproduce the problem.
For Dynamics 365 and Power Platform issues, also note whether the problem affects production or a sandbox environment. If the issue relates to Power Automate, include the flow name, run history, trigger, failed action, and correlation IDs where available. For Dataverse or model-driven app issues, include the table, app, form, view, business rule, plugin, or solution involved.
Before you open a Microsoft support request
- Confirm the issue is not limited to one browser profile or cached session.
- Check whether the issue happens for multiple users or only one user.
- Review recent solution imports, environment changes, security role edits, and connector changes.
- Capture exact error text instead of summarizing it from memory.
- Decide who on your team is allowed to approve diagnostic access or share logs.
After the ticket is submitted
Track the support request from the Support area in the Power Platform admin center. Keep the thread focused: add new evidence, answer Microsoft questions directly, and avoid mixing unrelated issues into the same request. If the issue is business-critical, document the production impact in plain terms so support can understand urgency.
For managed environments, keep a small incident log beside the support ticket. Record the date, symptoms, affected users, Microsoft request number, workaround, and final resolution. That log helps your team spot recurring platform, configuration, or governance problems.
Sources checked: learn.microsoft.com, learn.microsoft.com.
