Last year, Microsoft announced the public preview of Power Apps Ideas, which enables Power Apps makers to take advantage of Microsoft AI technologies that make it easy to write Power Fx formulas with no-code.
Please refer below article in which Microsoft is going to go behind the scenes to share what it took for the Power Apps engineering team to implement Power Apps Ideas and unveil some of the complexity that’s happening under the covers to support this user experience.
Microsoft announced the General availability of portals as a progressive web app that was introduced as a preview feature, enabling makers to enable portals into apps with native app like look & feel right from portal studio in just few steps! This is my favorite announcement for which I was waiting for…
Microsoft is leveraging Progressive web app technology (PWA) to enable portal to multi-platform supported app which works on all platforms (android/iOS/windows) as well as all form factors (mobile/desktop/tablet).
With PWA, end user can pin Power Apps portals as an app to the home screen on a mobile device or install it from the app store
This great new feature is stuffed with following capabilities :
Create low code-no code branded app in just few steps from portal studio
Manage basic offline experience of your app
Distribute your app via browser or app stores
Please refer the below link for more information –
To better accommodate the rapid expansion of Power Platform adoption across the enterprise, service administrators depend on advanced monitoring solutions. Tenant-wide analytics are built on service telemetry data derived from Power Platform apps, bots, and services. These solutions allow environment admins to effectively monitor activities related to Cloud flows across the organization. This update includes an expansion to the Data Export pipeline making Usage & Inventory metrics for Cloud flows available to Power Platform customers.
Microsoft introduced a set of new audit features helping Dataverse administrators to stay compliant with internal and external auditing requirements and to manage log capacity at the same time.
Audit data is now also stored in a separate physical log storage so an organization’s audit log can grow to many terabytes in size without limiting available physical database storage. This change in physical storage is independent from the continued need for having sufficient storage entitlements for logs and database records.
What is the auditing feature?
The auditing feature logs changes that are made to customer records and user access so you can review the activity later. The auditing feature is designed to meet the auditing, compliance, security, and governance policies of many regulated enterprises.
Audit retention policy
Administrators can select an audit retention period from a dropdown menu or specify a custom retention period. Audit records are automatically deleted after the retention period is over, relieving administrators from the burden of deleting audit data manually. It is also possible to keep the audit log indefinitely by not specifying a retention period.
Audit settings with the option to specify a retention period.
With new flexible audit deletion options, we are removing a major pain point our customers were facing frequently: how do I delete a subset of the audit logs while keeping the rest?
We are introducing a set of new audit deletion options so administrators can delete the logs of one or more audited tables, delete the user access logs, or delete logs up to a specific date in order to free up storage space. The new delete options are replacing the audit log management view and quarterly log partitions.