Power Platform Governance and Administration

PROBLEM

The Dataverse does not record milliseconds in its date/time columns.

We have various jobs in our source systems (not all under our own control) that produce changes in short periods of time.

In Dynamics we have plugins that attempt to locate and set the "current state" of various entities based on the LAST action taken.

IMPACT

Without milliseconds being available, some entities are set to the wrong "current state" because the code randomly selects one record from the set of records falling in the last second of activity as the entity's "last action".

This can have potentially legal ramifications.

SOLUTION

ALL columns in Dataverse need to support milliseconds.

This includes built-in columns (e.g.: createdon, modifiedon) as well as custom columns.

Allow for management of Power Platform app permissions within SharePoint, for SharePoint integration capability. Goal is to get away from the Sites.FullControl.All API currently used today from the SharePoint integration for Power Pages.

Initial support request details opened for this:

Support request ID

2401240040015793

Issue title

DCR request for SharePoint integration in Power Pages.

Issue description

In order for SharePoint (SP) integration to work, unfettered access to all of SP must be granted to the Power Pages backend Entra App, via the Sites.FullControl.All application type SP API. We have multiple use cases that we as a company are wanting to provide to our customers, in an ISV/SaaS like scenario, driven by Power Pages using it's SP integration feature for document management. We would like to request a DCR be opened for the Power Pages team. Specifically enabling this functionality to work using the Sites.Selected SP API and manage permissions for the Entra App directly in the SP site. This change would be more inline with a zero trust philosophy.

Currently it is not possible to restrict user access to the SQL TDS endpoint. Please update this to allow restrictions for users and groups.

When a candidate is created from the Dynamics 365 CRM portal in our system, it typically generated a new entry in our Case table with the owner listed as 'SYSTEM'. However, we've recently noticed that a new account named '# Microsoft CRM Portals' is being displayed instead. We would like to revert to the previous setup. Additionally, if possible, we'd appreciate having the flexibility to adjust this ourselves in the future.

Related document - https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fpower-pages%2Fadmin%2Fconnectivity%23migration-to-application-user&data=05%7C01%7Cm.demir%40irvn.nl%7C098c4e2fe1664337c7b108dbb8e70bed%7Ce0f12b69ac3e4ab19294efe7ab4695c5%7C0%7C0%7C638307074718452157%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WNJfftGrZr6ADJ2tX4gRvyPltHwnVyaDoN8p5h70FOQ%3D&reserved=0

After opening a ticket (MS 2308030040005931) it was deemed that, when clicking Related > Cases or Related > Activities within account and contact records, the 'associated' views cannot be defaulted to other useful views (such as 'All Activities' or "All Cases"). Having this ability will save seconds per instance, which adds up over time.

With the April 2023 update, the queue search now has an automatic value set, but we would like to add the ability to revert that setting.

The update should remove the default search value.

Currently it is not possible to scope a Conditional Access Policy for a specific Dynamics CRM instance. The only option is to instead scope the Common Data Service to the policy, however this would apply to all CRM instances.

The ability to scope specific Dynamics CRM instances would allow far more flexibility and granularity when creating conditional access policies.

Our organisation currently utilises multiple development environments for our CRM stack.

We would like the ability to scope different policies to our PROD and NON PROD instances.

Our client requested to have maker/checker capability for security updates like Changes in Organization Structure & Business Units, Changes in Teams / Queues management, Changes in Users & Security Roles Management. Would it be possible to update this feature to roadmap?

Increasingly functionality is being made available in Dynamics platforms/Power platform that can be linked to Azure subscriptions, examples are Application Insights and Dataverse Synapse link, these products need to cater for enterprises and administrators that have a wide range of Azure Access that exceeds the deemed 60 subscription limit that Microsoft seem to have assumed across all products, THis has been corrected for the synapse link, but not for the App Insights.

This issue surfaces everywhere and the most problematic areas are

1) Azure Devops - Service Pipelines

2) Azure Devops - Billing linked to Azure subscription

3) Dynamics/Power Platform - Application Insights/Synapse link

4) Power Bi - Premium Autoscale

The functionality also does not respect PIM scopes and just looks at what the user has access to without checking roles

What I would like to see is the ability to either scoll thru all subscriptions, or to be able to search for a specific subscription with either the name or ID. The search function would require the TenantID and the subscription ID and should then present a resource group list for selection.

This functionality should be a common object that can be utilised across all Microsoft products calling into Azure.

HI Team,

As currently we couldn't embedded power BI in iframe and since its byDesign I would request you to kindly please have this feature implemented in upcoming releases.

thank you.