Power Platform Governance and Administration

Microsoft recently released a new feature to "Block unmanaged customizations (Preview)".

So when "Block unmanaged customizations (Preview)" is enabled, please allow the Owners and Admins with CRUD Permissions for Unmaged Solution and its Objects.

This will be a supportive improvement related to another idea below

https://experience.dynamics.com/ideas/idea/?ideaid=144f18a9-9edc-ee11-a73e-002248504629

Recent changes to creating a developer environment from PPAC restrict Admins to 3 just like a self service sign up.

Admins are required to create many environments, for a number of projects that don't always want the developer environments to be assigned to a person, as they come and go.

Admins provisioning environments is NOT the same as some that wants to mess around and try something, where 3 personal environments is reasonale.

Remove the 3 environment limit for Developer environments when created in PPAC by Power Platform Admins.

Also, AUTO provision the trial SKU so admins don't have to ask a Global Admin to assign licenses.

Microsoft 365 is an emailing platform that many users trust and keep their data in it. Most organizations use Office 365 to store their crucial data; one can save personal and professional data. Users trust Office 365 because of its fantastic security features and subscription plan. It will allow users to keep their data protected; data is the most crucial asset for any user. Therefore, users are willing to migrate Exchange to Office 365 quickly without any delay.

Purpose to migrate the data

Now that users want proceed with the migration process, they want to check out its reason. However, most users are aware of the purpose of this migration process. Here we are sharing a few reasons for the same.

• Office 365 is available for users worldwide as it is a universal platform, so one can access their data whenever they want.
• Microsoft 365 has introduced a fantastic product that offers subscription plans, which allow users to extend their storage capacity.
• The security features of Office 365 make it a more reliable, which keeps user’s data protected.
• Users do not have to update it regularly and manually, as it will be automatically updated to the newest version.

What are the different methods to migrate Exchange to Office 365?

There are two methods to run the task: manual and professional third-party tools. Manually, the task will take time; as an old-school method, it will only migrate one data in a single go. Therefore, a professional third-party tool is the best option for users to migrate the data. Users are supposed to choose the tool carefully as there are many free tools available for the users.

Which tool is best for the task?

Users are asked to try the Weeom Exchange to Office 365 migration tool to begin the task. It is a trustworthy tool that will make the whole procedure easy easy-going for the users. The software comes with various security features, and we are sharing some of them here.

• The tool recovers the private and public EEDB files in a single go.
• The software will effortlessly finish the whole task without consuming much time.
• The filter r option allows the filter of the data based on the date range and message class.
• Users can resume the migration process with the help of the incremental export option.
• Users can add multiple mailboxes for the migration process.
• There is no size limitation so that one can add large-size files for the migration task.
• The tool can migrate the source mailbox into Outlook PST file format.
• The software supports every version of the Exchange server and Widow operating system.
• The software offers 24/7 technical support to the users so they can run this task whenever they want.
• It has a user-friendly interface that will make the whole procedure very easy-going.
• At last, users will get the entire task report to download and explore every tool feature.

Conclusion

We have shared all the essential details in the above content so users can go through the content mentioned above. The tool we have shared to migrate Exchange to Office 365 is one of the popular tools that offers a free demo version so that one can explore more about the tool.

Currently the only documented place where Power Platform administrators can discover the status of Dataverse for Teams environments scheduled for automatic deletion is the Power Platform admin center Environment page. On that page the deletion status of affected environments is indicated in the State column by the words "(Ready __ days until disabled)". Unfortunately, because there is no way to export the contents of that page, responsible admins are left with the labor-intensive task of manually copying and pasting the relevant information into Notepad, Excel or another app. Power Platform Admin Powershell and Power Platform CoE Kit queries are also unable to capture this information.

I would like to suggest either (a) the addition of export capability to the Environments page; or (b) an exportable report that provides detailed status information on each inactive dataverse such as the environment name, contacted owner, state, inactive date, warning date, disabled date, and deletion date.

Opening the admin portal, you can see the space consumption of each table. But you can't break down to the size of the data and the size of the index.

Therefore it's difficult to optimize the table, as at some tables, the index is the same size like the data.

It would be great, if during exporting the storage consumption to the excel, the used spaces is displayed as data and index in two columns.

I've been using Power Automate and encountered a bug in the "When a new email arrives (V3)" trigger. After applying a "For Each" action following the trigger, retrieving dynamic information like "ReceivedDateTime" doesn't yield the expected value. The issue lies in the trigger not automatically incorporating the "For Each" action, requiring manual updates to function correctly.

For sandbox environments, backups are retained for up to seven days. However, for production environments that have been created with a database and Dynamics 365 applications enabled, manual backups are retained for up to 28 days. 

Currently,we need Admin access, but unfortunately, we are not authorized to obtain Admin access as it is managed by a different team.

Consequently, we are looking for alternative options or solutions to monitor the daily backup without relying on Admin access.

Hi,

It would be great if you can provide support for Quick create form for Virtual Entities in model driven apps. The UI experience will be improved a lot!

Thanks

Michael

Need to enforce users to use the camera to take images and not to load images from their phone while using model driven power apps on the mobile.

This feature is currently not available. We were successful in hiding the upload button using java scrip when running the app using the browser but not on the mobile.

In power automate there is a missing feature to add comment under a MS Planner task right after its creation.

Reason: The ID of the communication thread for the asociated Group is not generated with the task, it is generated with first comment under said task.

Solution: Generate the ID of the communication thread with the creation of the Task.