Power Platform Governance and Administration

Our makers spend more time editing BlogPosts on our Portals websites - for news, articles, etc, than WebPages. Currently, PowerPages only allows for editing WebPages.

The Portal Management content editor is very poor for user-friendliness. Our makers' jobs would be much easier if everything to do with editing the website's content could be in one place.

It would be ideal if you could add the ability to create and edit BlogPost entities from the PowerPages Design Studio.

As the frontend content editor has been deprecated, this is a very high priority for our organization. Thank you for your consideration.

When editing using the Design Studio it only allows editing in the default language. 

In sites with multiple languages designed to use many snippets for localization content editors must use the Portal Management app to edit snippets out of context from the pages they occur on. 

It would be beneficial to be able to toggle the language of the portal in the designer to allow a preview of the content in said language and the ability to edit page copy and snippets in place. 

I don't know how Design Studio was released without the ability to choose the editing language.

Credit to Eric Sutter who first posted this 9 months ago in Power Pages Ideas Forum, which seems Microsoft does not monitor.

This feature is as important as ever with the new addition of conflict detection and merge features from VSCode for the web. 

https://powerpages.microsoft.com/en-us/blog/configuring-code-components-properties-from-the-design-studio-now-available-in-public-preview/

As the intention of Web templates as components | Microsoft Learn seems to be to allow makers to reuse these components easily - one glaring omission is that Design Studio lacks the ability to add custom components (Web Templates with manifests).

Seems like it would be an easy win to add a section for Web Templates and allow developers to open in VS Code.

The conflict resolution would be great to have. 

Additional thoughts on how to make working with Web templates better.

1. In web templates section have 2 or 3 collapsible groupings 
2. Components - Items with a manifest
3. Page Templates- Templates that are related to a page template
4. Other
5. Alternatively (since a Template may be a page template and have a manifest) Just having some sort of visual indicator for if manifest is present/is related to a page template
6. Add a GUI for working with manifest of a web template. Options in the '...' 
7. View Manifest - Show a pop up with manifest details so users know what templates inputs are and can read description
8. Edit Manifest - Would be nice to have a low code way of authoring manifest so user error is reduced
9. Create Component - If the web template was not a Component open editor to add component definition 
10. Selecting a web template in '...' Create Component then allow editing the manifest with low code tools. 
11. Add way to add a template as a component in the same menu as adding 'text', 'image', 'video','button', etc. 
12. Preferably multistep process where select "Component" then a listing of components including details from manifest I am thinking something similar to when you pick a PCF control on a model driven app. (Actually adding a thumbnail to web templates would be a cool concept too for the content editors to see perhaps a preview of what they are getting) 

Credit to Eric Sutter who posted this idea 9 months ago in Power Pages Idea forum - which doesn't seem to be used by Microsoft's product team.

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 Unmanaged 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

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

If a user copies data, e.g. account name, from a html source such as a company website and copies that data into Dynamics it could include the html-character NBSP which is usually is displayed as SPACE for the user. This special character should be replaced automatically with a SPACE for single line text fields.

One problem is that Sharepoint takes that special character also within its URL which could lead to problems using Power Automate with other systems.

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.

When we create a new Unmanaged Solution in Power Apps, it becomes visible to every Maker (System Customizer and Environment Maker roles)

When we create or add the existing objects (App, flows, Bot, Reports) to the unmanaged solution, the objects become exposed and every Maker (System Customizer and Environment Maker roles) in that environment will automatically gain CRUD permissions to the Unmanaged Solution and its objects' (App, flows, Bot, Reports) as well.

Security Concerns

• This has created a need for increased security rights over the Unmanaged Solution and its objects' (App, flows, Bot, Reports).
• This is causing more issues and fears to Makers about their Unmanaged Solution and its objects' (App, flows, Bot, Reports).

Changes Needed

• Please make the Unmanaged Solution visibility, and its Read, Update, Delete (RUD) permissions restricted to only the Solution creator and Admins in Power Platform.
• Please make the CRUD permissions for the objects' (App, flows, Bot, Reports) inside Unmanaged Solution restricted to only the Solution creator and Admins in Power Platform.

This is to make the unmanaged solution more secure and achieve an efficient ALM process

As we know Power Platform connection/link isn't reversible once the integration between the two systems is done. Disconnecting them would result in data loss as we only have the delete both instance option.

Given the scenario that, we are not able to refresh the data only in CE but not in FnO side. There is no reset option in PPAC as mentioned. The work around is having another CE available environment which we can use to perform a restore and get the desired result for the target CE environment.

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.