Admin.power Platform
Raul Herrera
I can see Licenses (Preview) Power Platform admin center (microsoft.com), but it seems inaccurate - it shows all my environments having 1 Trial licence, and doesn't show any Per App licences. No info on Users either.
go to Admin Center navigate to the "Billing" section in the left menu, proceed to "Licensee," and specifically click on "Power Apps Premium." Here, you'll find a comprehensive list of users currently allocated with Power Apps Premium licenses.
It seems like there might be a bit of confusion there. You should go to the "Environments" tab in the Power Platform Admin Center and then, within the specific environment where your apps reside, look for an option or tab related to licenses. It might not be directly under the "Environments" tab but within the options available for that environment. Try navigating through the options related to the specific environment, and you should find the license information.
within the Admin Center I can see the number of licenses associated with a specific app, but I cannot find the relevant users. It only says how many users the app is shared with. Where do I need to click?
thanks for the quick reply. Do you mean then Environments tab in the admin center or the Environments tab in the Licenses part of the admin center. Under Environments -> Enviornment I cannot find any button "licenses".
Power Apps per app licenses do not show up in Azure AD, as they are not assigned to users directly, but rather to environments and apps. You can check if a specific user has a per-app license assigned by using the Power Apps per-app plan assignment report in the Power Platform admin center. This report shows the number of app passes allocated to each user and the apps they have access to. You can also see the total number of app passes available and consumed in your tenant.
Checking Power Apps licenses can be a bit of a maze sometimes. Per App licenses might not show up directly in Azure AD as they are associated with the specific app rather than the user's overall license.
1. Power Platform Admin Center:
- Go to the Power Platform Admin Center (admin.powerplatform.microsoft.com).
- Navigate to the "Environments" tab.
- Select the environment where your apps reside.
- Click on "Licenses" to view the assigned licenses for that environment.
2. Power Apps Portal:
- In the Power Apps portal (make.powerapps.com), go to the "Apps" tab.
- Select your Canvas app.
- In the app details, you should see information about the number of assigned licenses and who they are assigned to.
We are excited to launch the public preview of the Data Gateway feature on the Power platform admin center; This feature provides tenant admins with visibility into all On-premises data gateways within their organization and also management capabilities.
This helps the tenant admin see gateway members in each gateway cluster. Clicking on the next to the Gateway cluster name display the gateway members. The detail includes the gateway member device name and the version of gateway on the device. Alternatively, you can also invoke this by selecting the gateway cluster and clicking on Open Gateways at the top.
Tenant admins can now add and remove gateway admins. Click on the icon for the gateway cluster. This will show the list of gateway admins. Alternatively, you can also do this by selecting the gateway cluster and clicking on Manage administrators at the top.
Similarly, tenant admins can also remove gateway admins. To do that, you would click on the icon next to the gateway admin of the gateway cluster in question. Clicking on Confirm below would remove the user from the list of gateway administrators.
Hi,
Im trying to find the setting to change the language in powerplatform admin center. In my o365 profile it's set to English and everywhere else, it is English which is used, but for some reason in this admin center it is my local language, which is a bit annoying. I went to the settings for the default environment (which i assume includes the power platform admin center?) and activated English but that made no difference. Is this possible to change somewhere?
After a first review of the end-user experience in my previous article, today Id like to take a closer look at Power Platform Pipelines from the admin perspective. So lets switch heads and drill into the typical requests upcoming from being a member of the Power Platform admin team that wants to use ALM for the good.
While Power Platform Pipelines recently was announced being general available, theres still some work to be done to fulfill on all above requirements and it also should be subject to roadmap if there will be integration scenarios with typical platforms known by code-first developers, such as GitHub or Azure DevOps.
Starting with the Admin Center experience first, where its about to configure your environments that you later on will be using for Power Platform Pipelines. From the visual above you can see that I configured a Power Pipelines environment as being my host for the solution. And due to testing purposes, I selected to go with a Developer Plan license for this exercise.
I was playing around with the Deployment Environments and added both a Microsoft Teams Environment as well as my Default environment which (you can check from Environment visual is configured for being Non-Managed Environment). To my surprise both where validated successfully and it worries me that even though documentation clearly stated that
are not leading to a validation failure in this case. So why? Why am I not provided a message that I cant use any of those environments? An answer that possibly only the engineering team can provide at this moment. Even admins like to be running through a smooth setup and configuration process and guided, instead of reading and following documentation. Hopefully, well see a rapid fix for this and integrate those checks inside the validation run.
So lets switch gears and take a look into the monitoring experience from an Admin perspective. How easy is it to identify an issue that occured when a Maker calls out for having a problem with deploying their solution. Therere two ways to drill into this. One is from the Pipelines configured and see the related Run history. Another one is to use the Navigation on the left and open the Run history from the section Deployments inside the Deployment Pipeline Configuration app.
From what can be visualized within the current Pipelines solutions you see a Managed Artifact File that is stored in ZIP format and it allows for being downloaded. Those knowing that on creation of a Dataverse record you can run a Power Automate flow would easily get the automation part to download the file automatically, extract it and check-in the artifacts in a source control system of your choice.
For my testing purposes, I exported a solution file from the UI and downloaded this file in addition. I then extracted both ZIP files and opened the solutions.xml to compare with Notepad++. As you can see both files are exactly the same.
Theres also work to be done to fulfill on further source control operations in terms of making it easy to identify code changes from an in-app experience or at least allow for an easy audit control of who made changes. Adding the Publisher or the prefix for instance to the details information of the artifact might help to simplify that task. Was it an individual performing these changes or was it a team working on features (both could be separated by using different Publisher in this case)
During my tests I stepped accross some interesting parts that I didnt want to miss out mentioning here as well. Both look promising and also shows that the roadmap ahead for Pipelines hasnt stopped by announcing it to be GA.
And in case of selecting one of them we also do find the list of Supoperations available shown in above visual. That leaves hope that there will be more Operation and Suboperation becoming available in future. Furthermore, them being used for individually perfoming an operation by configuring them. For instance using the Retrieving Artifact suboperation in a validation operation job and use it to generate the file without deploying it.
Number two I found inside the Deployment Stage Run by taking a look outside the General tab. Inside Deployment settings tab, you can find a Deployment Settings Json which is a setting that I actually couldnt configure during the creation of a Deployment Pipeline, nor a stage. So my hope is that this is something to become available and someone took a carefull look at Azure DevOps in terms of Deployment Jobs. Lets see what the future brings.
Beginning February 2024, Microsoft Power Apps is introducing a new endpoint for the Power Platform API as a service dependency change in the public cloud: *.powerplatform.com. The Power Apps end-user experiences will leverage this new endpoint. This change has been reflected in the documentation Power Platform URLs and IP address ranges.
If you employ in-house firewall rules to restrict network traffic to various URLs or IP addresses, you may need to adjust them to allow traffic to flow to endpoints under the following domain: *.powerplatform.com.
Renaming the environment through the admin center is recommended to make the purpose of that environment self-explanatory. Clearly communicate that Default is used for user and team productivity scenarios, but not business-important or mission-critical apps. This environment can't be disabled or deleted because it hosts integration with products like SharePoint and Project. We recommend a tiered approach to user and team productivity environments.
You can also control the set of connectors that can be used in the environment. You can find more on the connector blocking feature and the list of non-blockable connectors here -> -us/power-platform/admin/wp-data-loss-prevention.
When an environment is copied, the current method is to blank the email addresses in the LogisticsElectronicAddress table. This means that when the BYOD DMF export is run for Party Contacts or Worker Contacts it fails as the locator is a required field. The only way to stop this from happening...
93ddb68554