Share via

Help us help you with Power Platform

  • Article

In addition to the general questions and points covered in the following sections, the specific support teams for Power Platform often require additional information for the topic. This article contains tips for supporting solutions with Power Platform and Dynamics 365 apps. Find the section that aligns with your issue in the following sections. For unique or uncommon issues, there might not be a specific section; in such cases, refer to the general guidance page on what information to submit. Also, we recommend that you review the provided troubleshooting links before opening a case. Providing clear and detailed information in the support ticket helps the support engineer address the issue more efficiently and in a timely manner.

Technical

For troubleshooting specific finance issues, review the following article: Microsoft Power Platform troubleshooting

Storage (out of capacity)

  1. Do you know how capacity works?

  2. Your capacity displays as 0% for all sections means that you don't have a valid Dataverse subscription. Reach your Microsoft reseller or billing team for more details.

  3. You can see all details about your storage consuming through Power Platform admin center, do you know where?

  4. Using this article, you can see which environment is consuming more, which section and top 10 tables.

  5. For your knowledge, Database = Records / File = Attachments (Azure Blob) / Log = Plugin Trace and Audit (Cosmo).

  6. You don't know what exactly this table means or how to perform maintenance. Learn more in the following article:

  7. TDS connection is also an option to check the number of records per table mainly for AsyncOperationBase and ActivityPointerBase:

  8. Remember, without storage you're out of compliance and can't create new environments, copy, or restore environment. Also, a recurrent email notification is sent weekly reminding you about it.

  9. Some tables are more complex and might need a deeper analysis from your side. The following list provides links to where you can learn more about some of these tables.

  10. Developer environments, Microsoft Teams environments (2 GB), Support Instances that Microsoft Support creates, and Default environments (3 GB) don't consume storage:

Licensing

  1. Always check the latest version of the licensing guide.

  2. Do you know how the license model works?

  3. Remember about default storage granted by subscription and the amount of storage granted for full licenses.

  4. Default storage isn't cumulative for Dynamics 365, Power Platform, or Project licenses.

  5. The Dynamics 365 Team Members subscription is a named user subscription that includes rights to run basic processes across Dynamics 365 apps. This way, business users can share knowledge and provide embedded business intelligence. One Team Members subscription enables a light user to read from any of the Dynamics 365 applications. As a result, as more Dynamics 365 applications are adopted across an organization, any user previously licensed with a Team Members subscription would be licensed already to access those more applications.

Synchronize users

  1. Did you check about unaccounted user issues article?

  2. Did you use the tool User Diagnostic? Using this tool, you can identify issues related to licenses, roles, security groups, and nested security groups.

  3. Read the article about different users like Application User, Non-Interactive User, Administrative User:

  4. Remember, your user can be a Cloud User, Synchronized User, or a Federated User.

  5. Also, CA (Conditional Access) policies also could cause access issues:

Limitations for guest user must be considered:

Lifecycle operations (Create, Copy, Restore, and Delete)

  1. You only can restore a production environment to a sandbox environment.

  2. Backup for production is retained for 28 days, for sandbox only seven days. There's no way to extend this period, including on-demand backup.

  3. You only can copy a managed environment to a managed environment.

  4. After deletion, you can restore the deleted environment in the next seven days.

  5. Default environments are limited. Any operation needs Microsoft support help.

  6. Lifecycle operation persists for 48h before failing completely. The lifecycle process passes through different steps; each one cared for by different teams.

  7. An environment can be unmanaged through PowerShell commands:

  8. More about environment types:

Migrate environments from tenant to tenant or from region to region

Leave us feedback

Is there anything else you need help with? Leave us feedback.