Weekly Digest for usage insights | Power Platform Admin Center

One of the features in Power Platform Admin Center is that now you can receive Weekly Updates in the form of a Newsletter for the Managed Environments.

Pre-Requisites

Below are the Pre-requisites for enabling Weekly Digest

  1. Tenant-Level Analytics must be enabled in your Power Platform Tenant. Here’s a post to see how you can enable Tenant-Level Analytics – Tenant-Level Analytics in Power Platform Admin Center | For Power Apps and Power Automate
  2. Only Managed Environments Updates are available – Here’s how you can learn more about Managed Environments – Enable Managed Environments in Power Platform Admin Center
  3. Under those Managed Environments, only those Managed Environments will be considered which have been enabled for Weekly Digest. While enabling Managed Environments in the above step #2, ensure this checkbox is marked in order to consider the Managed Environment for Weekly Digest –

Enable Weekly Digest

Given the above Pre-requisites are met, here’s how you can enable Weekly Digest –

  1. Navigate to Tenant Settings in the Power Platform Admin Center (https://admin.powerplatform.microsoft.com/tenantsettings) – Look for Weekly digest. Notice that it is marked with a green icon which indicates that it will only be applicable for Managed Environments.

  2. On the right hand side, you’ll see place to enter email addresses (separated by semicolons) who should receive the Weekly Digest emails.
    Power Platform Administrators and Dynamics 365 Administrators only will receive these updates.

  3. Once you entered the email addresses, you can Save those and you’ll see the below message upon confirmation.

  4. That’s it!
  5. And then on a Monday, I saw this in my mailbox!

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Advertisement

Enable Managed Environments in Power Platform Admin Center

Here’s what Managed Environments do! They provide more control on how you administer the Environments i.e. by limiting App Sharing, applying Data Policies on the environment and even how Solution Checker should allow to import solutions upon detecting critical issues (Solution Checker feature for Managed Environments is in Preview at the time of writing this post!).

Below is the snipped from Microsoft Learn Document highlighting the capabilities of Managed Environments



Further, as I explore these features more, I’ll update and add links to the posts explaining each of the features in details.

Enable Managed Environments in Power Platform Admin Center

Given that you have appropriate permissions to take administrative actions on Power Platform environments, you can navigate to Power Platform Admin Center and then in Environments (https://admin.powerplatform.microsoft.com/environments) –

  1. Select an Environment and click on the ellipses on the menu.

  2. Once you select the same, review the License implications as highlighted below –
    Here’s the Microsoft Documentation on the same – https://learn.microsoft.com/en-gb/power-platform/admin/managed-environment-licensing?WT.mc_id=ppac_inproduct_env%3FWT.mc_id%3DDX-MVP-5003911

  3. Once you review the below preferences on how you want this environment to be managed, you can select the same and click on Enable as seen below –
    These will send insights in email. I’ll cover in a separate post and link here.


  4. Once everything looks good, you can Enable.

Editing Managed Environments / Disabling

Here’s how you can edit or disable Managed Environments –

  1. If you are seeing Edit Managed Environments, it means that Managed Environment is enabled for that environment.

  2. And you can disable Management Environment control using PowerShell. You can check this post which highlights how you can do so – https://learn.microsoft.com/en-gb/power-platform/admin/managed-environment-enable#disable-managed-environments-using-powershell?WT.mc_id=DX-MVP-5003911
    Snapshot of the document below –

Here’s Microsoft Learn documentation on Managed Environments – https://learn.microsoft.com/en-gb/power-platform/admin/managed-environment-overview?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Power Platform self-service analytics Data Export to Data Lake [Preview] | Power Platform Admin Center

Now, you can also export the Analytics Data to Azure Data Lake in order to further extend the derive rich data analytics!
At the time of writing this post, this feature is in Preview (As you’ll also see from the screenshots below)

This is a great feature where you can extract this Data into Data Lake and then further enrich and derive rich Power BI reporting based on your use-case.

In case you are new to understanding Azure Data Lake and pricing, you can review this – https://azure.microsoft.com/en-gb/solutions/data-lake/?WT.mc_id=DX-MVP-5003911

Data Export (Preview)

In Power Platform Admin Center (https://admin.powerplatform.microsoft.com/), here’s how you can setup Data Export –

  1. Navigate to Data Export in Power Platform Admin Center given that you have appropriate rights –


  2. Then, you’ll get to choose amongst the Power Apps or Power Automate data to be exported to Data Lake.

  3. In this example, I’ll choose Power Automate. As I select Power Automate, you’ll see that Tenant-Level Analytics are required and hence, already considered as Yes. If not, you’ll need to Enable Tenant-Level Analytics while doing this step – Here’s another post on how to Enable and Use Tenant Level Analytics –


  4. Now, In the next section you’ll need to choose the Subscription.


  5. Further, select the Resource Group and eventually, the Storage Account as well.


    And Storage Account is selected as well.

  6. Once everything looks good, you can click on Create.

  7. In a few moments, this will appear in Data Lake section of the Data Export. It will take up to 24 hours for the data to first start showing in Data Lake.

  8. Once this is completed after about 24 hours, you’ll see the status of the Data Lake data package changed to connected.


Data Export to Data Lake

Let’s look at the Azure Storage Explorer to connect to our Data Lake and see the Power Platform data – In case you are looking to install Azure Storage Explorer, here’s a post – Microsoft Azure Storage Explorer | Getting Started

  1. Once authenticated to the correct environment in Azure Storage Explorer, here’s what you would see in the ADLS Gen 2 (In case you want to create ADLS Gen 2 storage account, you can review this post – Create ADLS Gen 2 Storage Account for Azure Data Lake)
    You’ll see powerplatform folder show up.

  2. If you open this folder, since we had chosen Power Automate, it’s folder will be created.

  3. And let’s go in Flows folder to see the data. You’ll find json files of the same. You can double click to open it and it’ll open in whatever editor you have installed.

  4. In this case, I had VS Code, so here’s what the Flow data looks like –

  5. Likewise, you can dig deeper in this data and use this further for your reporting!

Here’s Microsoft Learn Document on the same – https://learn.microsoft.com/en-us/power-platform/admin/self-service-analytics?WT.mc_id=DX-MVP-5003911

Here’s Microsoft Learn Docs for Tenant-Level Analytics – https://learn.microsoft.com/en-gb/power-platform/admin/tenant-level-analytics#how-do-i-enable-tenant-level-analytics?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Run User Diagnostics in Power Platform Admin Center | Solving User Access Issues for Dynamics CRM

Many users often reports issue of not being able to access Dynamics 365 CRM even when they’ve been assigned security roles.

So, Power Platform Admin Center will provide you a Diagnostic Tool to quickly check what type of access is missing at the administration level across the below areas –

  1. Sign in blocked for the User at M365 level.
  2. No license for Power Apps / CE Apps.
  3. Not in Security Group of the Dataverse/CRM environment

Let’s see how we can run the Diagnostics and how to solve each of them!

Run Diagnostics on Users

Here’s how you can Run the Diagnostics on the Users in Power Platform Admin Center –

  1. Navigate to the Settings once you select the Environment –

  2. Then, expand the Users + permissions area to see the Users option

  3. Once you see all the Users, you’ll be able to see which Users you want to select and then investigate for diagnostics.

  4. When you click on Run Diagnostics, you’ll see the pan on the right hand side complete some tests and then show the results –

  5. And when you zoom, you’ll see the information as below –

  6. So, when you check the License information in the M365 Portal (considering you have Admin access), you’ll identify that the User is missing the license for Power Apps / Customer Engagement Apps.

  7. When I run this for User whose all levels of access are correct, I’ll see the below –

  8. In other instances, the Sign-in could be blocked as well and this is how it’ll appear. The error message will point out what is causing the User to not access the Dataverse environments.

  9. And when you check the User in the M365 Admin Center, you’ll see that the Sign-in is blocked –

  10. And a final reason that a User is not a part of the Security Group which has been assigned to the Environment itself.
    In that case, they’ll see the below error –

  11. So, if you check the Environment in PPAC itself, you can see what Security Group has been applied to the Environment.

  12. And if you look at this Group, you’ll not find the member in the Security Group at the M365 Level.

You can find the complete Microsoft Learn documentation on the same here – https://learn.microsoft.com/en-gb/power-platform/admin/troubleshooting-user-needs-read-write-access-organization#user-diagnostics?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Schedule maintenance updates should occur for Dynamics 365 CRM environment | Power Platform Admin Center

In case you are seeing issues lately that you are not able to access your Dynamics 365 CRM or it’s running relatively slow, it might be perhaps because the platform is being updates from Microsoft’s end for importing solutions in your environment as platform updates.

System freeze could happen if any solutions are being imported into your environment. Now, you can control when the updates should be allowed so that you don’t get downtime during your business hours. Let’s look at this!


Maintenance Window Settings in Power Platform Admin Center

Given that you are already aware on how you can go to Power Platform Admin Center (https://admin.powerplatform.microsoft.com/) –

  1. Navigate to Environments, select the Environment which you want to check the Apps Updates schedule and click on Settings.

  2. Once in Settings of the Environment, you’ll see the Updates section which you can expand and you’ll see the Maintenance Window Settings – So remember, this is still in Preview as of yet and might not work as expected unless it’s in GA.

  3. And this will let you set the time frame based on when you want to Updates to be applied to the environment.
    It’ll show that it’s currently set to 02:00 to 11:00 UTC – which is not favorable for my based on my working hours since I’m in India.

  4. So, I’ll check on a service like https://www.worldtimebuddy.com/ and make sure I compare and see when is the best way to schedule my updates for –
    Currently, the above updates are scheduled for 07 am IST which won’t suit my needs.

  5. So, I’ll change it to some other time! So, something like 15:00 UTC works for my which skips my usual business hours so that my business hours are not interrupted with Updates on the platform.

    So, I select the new time and click Save. I can expect about 48 hours for this to come into effect even though updates are usually pushed over the weekends and not weekdays.
  6. You can read this Microsoft Docs on Maintenance Window Settings here – https://learn.microsoft.com/en-gb/power-platform/admin/manage-maintenance-window?WT.mc_id=DX-MVP-5003911

Check Solutions History

In order to check if your CRM environment is not working as expected, as an Administrator you can always to Power Apps (https://make.powerapps.com/) –

  1. Make sure the correct environment is selected, then

  2. Then, in Solutions, you can see History tab which will show the recent App Updates applied.


  3. And as you see above, the updates were taking place based on what my old settings were set. Hence, I needed to change the same to ensure my business hours are not affected.

Hope this was useful and this helped in clarifying the concept!

Here are some Power Automate posts you want to check out –

  1. See Trigger Outputs using Edit Columns in Flow Runs | Power Automate [Quick Tip]
  2. Adding Image field on the form in Dynamics 365 CRM | Power Platform Modern Form Designer [Quick Tip]
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Users cannot create Flows in Power Automate | Environment Maker permissions

If you are someone who has been asked to create Flows in Power Automate, and you go to Power Automate portal (https://make.powerautomate.com/) to make your first Flow in your environment, you may come across this if you are not an Administrator yet –

The error message would say -“You are not permitted to make flows in this ‘<EnvironmentName>’. Please switch to the default environment, or to one of your own environment(s), where you have maker permissions.

Now, let’s see what the issue is about.

Environment Maker Permissions

As a Power Platform Administrator yourself, you’ll need to provide Environment Maker privileges (Security Role) to the affected User in your environment –

  1. Navigate to the the Settings for the Environment in PPAC (https://admin.powerplatform.microsoft.com/)
    And look for Security Roles in Access area –

  2. Look for the Environment Maker role.

  3. When in Environment Maker role, look for the Add People button on the top.

  4. Now, search for the user who should have the Environment Maker permissions and click Add (which will be at the bottom of the pane).

  5. Now, you’ll see that this user is added.

  6. Now, when the User will refresh the Flow Editor, they’ll no longer see the error message and will be able to create/save Flows.

Hope this was useful!

Here are some Power Automate posts you want to check out –

  1. Blocking Attachment Extensions in Dynamics 365 CRM
  2. Upgrade Dataverse for Teams Environment to Dataverse Environment
  3. Showing Sandbox or Non Production Apps in Power App mobile app
  4. Create a Power Apps Per User Plan Trial | Dataverse environment
  5. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  6. Co-presence in Power Automate | Multiple users working on a Flow
  7. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  8. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  9. Call a Flow from Canvas Power App and get back response | Power Platform\
  10. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  11. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  12. Asynchronous HTTP Response from a Flow | Power Automate
  13. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  14. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Customer Lockbox (preview) in Power Platform Admin Center | Dynamics 365

Often, it’s a dilemma for partners when Microsoft support asks for access to the environment or making a “copy of the affected environment” in order to review an issue at hand. This is a super-helpful feature where we get to see what is being accessed in order to review data.

Microsoft Docs Link to Customer Lockbox (preview) – https://docs.microsoft.com/en-us/power-platform/admin/about-lockbox?WT.mc_id=DX-MVP-5003911

Please note that this is a preview feature and not meant for Production use. Currently, this also doesn’t cost anything and a cost will be associated once this is out of preview. Read the above Microsoft Doc to learn further.

Let’s look at the summary of this feature –

What is this feature?

  1. If you raise a Microsoft Support Ticket or Microsoft identifies an issue with your environment and needs to take a look at data, this feature comes handy in providing controlled access to data.
  2. If any issues need Production data to be investigated which could be business-sensitive, you can provide controlled access to Microsoft Support and also review/Audit such an access.

I’ll update further on –

  1. Whether review requests can be raised by partners who don’t have production access but have access to Sandboxes only based on Security Group practices some organizations generally follow. Or is only Microsoft can initiate a request?
    Here’s a post I put up in Power Platform Forum for the same – https://powerusers.microsoft.com/t5/Power-Apps-Governance-and/Customer-Lockbox-for-partners-same-tenant-access/m-p/1685530#M6849
  2. What is costs since in preview (at the time of this post), this is free-of-cost but will be chargeable once out of Preview.
  3. Once I create an actual Support Ticket with Microsoft and if they request access to Production data, I’ll configure a Lockbox scenario and update this blog further.

Customer Lockbox settings in PPAC

In Power Platform Admin Center [PPAC] (https://admin.powerplatform.microsoft.com/) –

  1. Look for Customer Lockbox (preview) under Policies section as shown below.

  2. Once you are in Customer Lockbox, you’ll see a button to start Configuring Customer Lockbox. While in preview, this is free – Later, it will be chargeable.

  3. Once this turns on in a few moments, you can see the message come up explaining how the Customer Lockbox will be enabled in 24 hours.
    The message reads – “For the duration for the preview, enabling Customer Lockbox will apply to all environments in the tenant. This capability is available in preview at no cost. When this feature becomes generally available, there will be a cost associated with environments protected by Customer Lockbox.

  4. Post this, you can turn the switch On and Save the settings. It’ll take 24 hours to take effect.

Hope this was helpful! Here are some more Dynamics 365 posts which you might be interested in –

  1. Dynamics 365 Storage Utilization | Dataverse Storage | Power Platform Admin Center
  2. Use Hierarchy in Roll Up Fields in Dynamics 365 CRM
  3. Filter records in a View owned by a Team you are a member of | Dynamics 365 CRM
  4. Get GUID of the current View in Dynamics 365 CRM JS from ribbon button | Ribbon Workbench
  5. Dynamics 365 App For Outlook missing on SiteMap in CRM? Use shortcut link [Quick Tip]
  6. Import lookup referencing records together in Dynamics 365 CRM | [Linking related entity data during Excel Import]
  7. Mailbox Alerts Hide/Show behavior in Dynamics 365 CRM
  8. Excel Importing Notes (Annotation) entity in Dynamics 365 CRM
  9. Enable/Disable the need to Approve Email for Mailboxes in Dynamics 365 CRM CE
  10. Call Azure Function from Dynamics 365 CRM using Webhooks
  11. Show Ribbon button only on record selection in Dynamics CRM
  12. Accessing multiple occurrences of a field in Business Process Flow using JS in D365 CRM

Thank you!!

Upgrade Dataverse for Teams Environment to Dataverse Environment

Given that you have licenses already in place along with the required Capacity in order to Upgrade from Dataverse for Teams to Dataverse, upgrading the same is an extremely easy process –

Upgrade to Dataverse

In case you have Dataverse for Teams environment and you want to upgrade to Dataverse, here’s what you do in the Power Platform Admin Center (https://admin.powerplatform.microsoft.com/)

  1. Go in the Dataverse for Teams (Microsoft Teams) type of Environment and look for the Upgrade button on the top right corner.

  2. Here’s what the Welcome Page looks like, make sure you understand the operation you are doing as this is permanent and cannot be undone!
    Here’s the detailed Microsoft Documentation on the difference between Dataverse for Teams and Dataverse itself – https://docs.microsoft.com/en-us/power-platform/admin/about-teams-environment?WT.mc_id=ppac_inproduct_env#promotion-process?WT.mc_id=DX-MVP-5003911

  3. Once you clicked on Next, you’ll need to agree to Terms and then confirm the same. Again, this operations is a permanent and can’t be reversed.

  4. It’ll start the process just like any other standard environment change process in Power Platform Admin Center (https://admin.powerplatform.microsoft.com/)

  5. This is how it will look while it is being Upgraded.

  6. This took over 1-2 hours. And once done, your environment will be upgraded.

Hope this was helpful!

Here are some Power Automate posts you want to check out –

  1. Create a Dataverse for Teams environment and add a Canvas App in a Channel
  2. Showing Sandbox or Non Production Apps in Power App mobile app
  3. Create a Power Apps Per User Plan Trial | Dataverse environment
  4. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  5. Co-presence in Power Automate | Multiple users working on a Flow
  6. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  7. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  8. Call a Flow from Canvas Power App and get back response | Power Platform\
  9. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  10. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  11. Asynchronous HTTP Response from a Flow | Power Automate
  12. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  13. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Show only configured Activities Related records section | Power Platform Admin Center

Here’s a setting which I personally don’t think would matter much and I’ll get to why I think like that.

Show Activities only configured in the App

Let’s navigate to the Settings for the organization in the Power Platform Admin Center (https://admin.powerplatform.microsoft.com) –

  1. Click on Settings once you are in the environment which you want to configure this feature.

  2. In Settings, go to Features.

  3. In Features, you can scroll to the bottom and see this option.

  4. What this Turned Off feature does is show all the Activities in the (example: Sales Hub) App -> Related section of the records’ + New Activity button


    And the + New Activity button in the Activities Associated View will show all the Activities by default regardless if they are configured in the App or not.

  5. However, the gripe is that this doesn’t reflect in the Timeline control by default. You have to change the options in the Timeline control separately. (And the Timeline is the most common way you would create an Activity, right?)

  6. Now, let’s turn this setting On and see the effect.

Turned On

Now, when this is turned on, the Activities’ Associated View’s + New Activity button will only show the Activities which are included in the App itself and not all.

I wished this was also reflected easily on the Timeline control and in the Main Activity View as well from it’s own entity in the SiteMap. Perhaps it could be work in progress. I’ll clarify once I know more! 😊

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobile app
  2. Create a Power Apps Per User Plan Trial | Dataverse environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  4. Co-presence in Power Automate | Multiple users working on a Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  7. Call a Flow from Canvas Power App and get back response | Power Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  10. Asynchronous HTTP Response from a Flow | Power Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  12. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Create Application Users for Dynamics 365 environment | Power Platform Admin Center

Here’s how you now set up Application Users in Dynamics 365 CRM from the Power Platform Admin Center instead from the Classic UI and let’s see how the process is eased.

Classic UI

Previously, you used to see Application Users view in the Dynamics 365 CRM under Settings > Security > Users.



But it’s not longer available. Instead, you now go to the Power Platform Admin Center.

Register App in Power Platform Admin Center [PPAC]

Now, once you are in the Power Platform Admin Center, you can go to the Environment section –

  1. First, let’s say this is your App in your Azure’s Active Directory in the App Registrations. And now you want to create an Application User in Dynamics CRM for this App.

  2. Now, you can go to the PPAC and in Environments, look for your D365 CRM/Dataverse environment.

  3. In Settings, you’ll see Users, expand the same and you’ll see Application Users which is now it’s own separate option.

  4. Now, you’ll see the Registered Apps I have already and you can add from the “+ New App User” button above.

  5. Now, select the + Add an app button

  6. And you’ll see the complete list of all the Apps that are in your Azure’s Active Directory. Select the one your just created and click Add.

  7. And then finally click Create once you Add the App you want to create Application User for.

  8. And now, you’ll see the App added as an Application User for your environment.

  9. Now, you also need to provide Security Roles based on the requirement. Select the App User, and click on Edit security roles once available.

  10. In my case, I’m giving 3 Roles which I need to give and click Save.

  11. Now, I’ll also see how many Roles have been given to the App User.

Hope this was helpful! Here are some more Dynamics 365 posts which you might be interested in –

  1. Setup Postman to connect to Dynamics 365 CRM using OAuth 2.0 | Azure App Registration
  2. Dynamics 365 Storage Utilization | Dataverse Storage | Power Platform Admin Center
  3. Use Hierarchy in Roll Up Fields in Dynamics 365 CRM
  4. Filter records in a View owned by a Team you are a member of | Dynamics 365 CRM
  5. Get GUID of the current View in Dynamics 365 CRM JS from ribbon button | Ribbon Workbench
  6. Dynamics 365 App For Outlook missing on SiteMap in CRM? Use shortcut link [Quick Tip]
  7. Import lookup referencing records together in Dynamics 365 CRM | [Linking related entity data during Excel Import]
  8. Mailbox Alerts Hide/Show behavior in Dynamics 365 CRM
  9. Excel Importing Notes (Annotation) entity in Dynamics 365 CRM
  10. Enable/Disable the need to Approve Email for Mailboxes in Dynamics 365 CRM CE
  11. Call Azure Function from Dynamics 365 CRM using Webhooks
  12. Show Ribbon button only on record selection in Dynamics CRM
  13. Accessing multiple occurrences of a field in Business Process Flow using JS in D365 CRM

Thank you!!