Power Platform Governance and Administration

https://learn.microsoft.com/en-us/power-pages/configure/manage-sharepoint-documents#step-1-enable-document-management-functionality-in-model-driven-apps

Global admin role is required within Azure for activating the integration which only works when the operator is directly assigned to the role rather than when a group is assigned to the role.

This goes against our rbac and pim model

Title: Allow PPAC Admin User to Unlink and Relink the CE Environment with F&O Environment

Overview:

This proposal suggests implementing a feature that empowers PPAC admin users to unlink and relink the Customer Engagement (CE) environment with the Finance & Operations (F&O) environment directly within the PPAC. This functionality aims to facilitate more efficient management of environments, especially for businesses that require frequent synchronization between production and lower environments.

Detailed Description:

1. Current Challenge:

• Businesses often need to perform a weekly refresh from production to lower environments or shadow environments to maintain up-to-date backups and ensure testing environments reflect production data.
• Currently, the unlink-relink process requires opening a support ticket with Microsoft. This is both time-consuming and dependent on the availability of Microsoft's technical support team, which may not align with the business's operational downtime.

1. Proposed Solution:

• Introduce a feature in the PPAC that allows admin users to unlink and relink the CE environment with the F&O environment without needing to engage Microsoft's support team.
• This feature would be accessible to users with the necessary administrative privileges, ensuring that only authorized personnel can perform these actions.

1. Benefits:

• Efficiency: Reduces the time and effort required to manage environment synchronizations, allowing businesses to perform these actions independently and on-demand.
• Flexibility: Businesses can schedule unlink-relink processes according to their operational needs without waiting for external support, minimizing downtime and disruptions.
• Cost-Effectiveness: Decreases the reliance on external support, potentially reducing costs associated with support tickets and downtime.

1. Considerations:

• Security: Ensure that the feature is secure and that only authorized users can perform unlink-relink operations. Implement authentication and logging mechanisms to track changes.
• Usability: Develop a user-friendly interface within the PPAC to guide admins through the unlink-relink process, including any prerequisites or dependencies.
• Documentation: Provide comprehensive documentation and best practices to help admins understand the implications and proper steps for unlinking and relinking environments.

1. Implementation Steps:

• Conduct a feasibility study to understand the technical requirements and potential impacts on existing systems.
• Develop a prototype to test the unlink-relink functionality within a controlled environment.
• Engage with a pilot group of users to gather feedback and refine the feature.
• Roll out the feature to all PPAC users with appropriate training and support materials.

Conclusion:

By allowing PPAC admin users to unlink and relink environments independently, Microsoft can significantly enhance the flexibility and efficiency of environment management for businesses. This feature aligns with the need for agile and responsive IT operations, supporting businesses in maintaining robust and up-to-date environments.

This proposal should provide a comprehensive overview and rationale for the suggested feature, making it easier for the Microsoft team to understand the value and importance of the enhancement.

We can see that Power Pages has a firewall capability now. This feels like a great step toward more control of traffic through Power Pages.

I work with quire secure Government departments and they often have an issue with the lack of logging and antivirus capability with Power Pages.

Traffic monitoring is currently very elementary. What my clients often want is the ability to track the IP address a given user (logged in portal user) came from and what pages they visited, what forms they drafted, etc. We can come close to this info through the use of analytics with DNS forwarding, but it's still not a bullet proof data match.

Is there anything on the roadmap to improve this level of logging?

We can see that Power Pages has a firewall capability now. This feels like a great step toward more control of traffic through Power Pages.

I work with quire secure Government departments and they often have an issue with the lack of logging and antivirus capability with Power Pages.

Antivirus needs to be managed after the file is uploaded and landed on the network. Although it is secure, some government security standards stipulate that they need the file to be scanned before landing into the secure network's storage. In the past we'd use F5 to scan during transmission. Is it possible to enable the new firewall to scan files prior to it landing into Storage blob, sharepoint or Annotations?

I understand that we have Defender for Cloud and Storage which I'm a fan of, but for it's not so simple for Annotations. Also sometimes we have old, outdated policies we simply can't get around.

It would be great to receive a reminder when the website authentication key is due for renewal, I had an internal company site that is used quite heavily within the firm down for just under a week because of this with no indication as to what the cause was, After checking all of the site settings and scouring my code for errors a simple refresh of the authentication key was all that was required. A lot of hassle for a tiny problem.

Either an email reminder to the owner or a notification when editing the site to say that the key needs to be renewed would be great

Issue

ADB2C's login page is currently reading the URL parameter ui_locales.

This param is always passed in by PowerPages with the Site's Default Language setting value from the site management page when being redirected to the B2C.

This completely disables the ability to rely on the browser's language to show the good messages to the end user.

Idea

That would be great to have a checkbox just under the default language field like Do not pass the language to the B2C.

When this is checked, this would not pass the param anymore.

Current workaround

Use a custom B2C javascript to redirect the browser with the correct ui_locales param (actually depending on the browser's language) if the language does not match. Quite hackish but we are currently using that solution with our customers without too much complain.

HI Team,

I am using OOB Calendar column in power apps and the view is working perfect in the format however when I view the same form in power pages the view and format is missing and I can see only in a text format. It would be great if you implement the supported features in near future . Thanks

Currently, there is no out-of-box method apart from Export to Excel, which has a 100k rows limit, to achieve this, and the recommended alternative is via an environment Copy, or a 3rd party tool.

Benefits:

- Simplifies the migration process for individual entities

- Ensures consistency and accuracy across different environments

- Reduces the time and effort required to learn the 3rd party tool

Use Case:

This feature would be particularly useful in scenarios where specific entities need to be migrated or moved to a separate testing environment without affecting the entire organization. It would greatly enhance the flexibility and efficiency of entity management, enabling seamless transitions and consistency.

Thank you for considering this request. I believe it would be a valuable addition to the platform and greatly benefit users.

Currently, there is no out-of-box method to do this, and the recommended method is via an environment Copy, or a 3rd party tool.

Benefits:

- Simplifies the migration process for individual entities

- Ensures consistency and accuracy across different environments

- Reduces the time and effort required to learn the 3rd party tool

Use Case:

This feature would be particularly useful in scenarios where specific entities need to be migrated or moved to a separate testing environment without affecting the entire organization. It would greatly enhance the flexibility and efficiency of entity management, enabling seamless transitions and consistency.

Thank you for considering this request. I believe it would be a valuable addition to the platform and greatly benefit users.

When using the API call to "/api/data/v9.0/organizations", the value for "auditretentionperiod" does not reflect the audit retention period setting in admin center. However, the value is updated correctly for "auditretentionperiodv2", which can cause confusion to customers. The "auditretentionperiod" attribute should be removed to avoid confusion.