You’re offline. This is a read only version of the page.
31
Hi,
We have managed to deploy canvas apps and flows in a solution to another environment using azure pipelines and power platform build tools. But after deployment, we are not able to share the app with other users even if we are system administrators in the environment. Can some one help me understand why as a system administrator I am unable to share the managed canvas app with other users?
When I use the following command to change the owner of the app, I am able to then Share it with other users. But surely this is not the right way to do this: Set-AdminPowerAppOwner -AppName $app.AppName -EnvironmentName $environmentName -AppOwner $Global:currentSession.userId
Can some one give me guidance on how to deploy a solution as a managed solution to other environments and then share it with other users. What would happen if we share version 1.0.0.1 of the app then re import version 1.0.0.2 - will the permissions stay intact?
Feels like the whole concept of solutions and environments is a half baked and served !
Note also that for Automate Service Principals are now supported. Hopefully this will not prevent sharing as it seems to have in the past.
You can use an AD 'Service Account' instead that has no MFA and this will be the owner instead of a service principal. It will allow you to log in as that AD account and at least manage the apps/flows sharing.
You can also assign, O365 groups but this is not an option in the Import Task for Power Platform Tools. You'd have to do this manually.
There seems to be a limitation in the browser management that doesn't exist in the CLI. I've run into this before. There's probably different product teams and they are all releasing functionality in different orders.
@vammers
There are some benefits and purpose behind having ALM handle everything in production as @byrnep mentioned, ALM should also handle the sharing. But as ALM may still have some wrinkles to iron out at the early stages, there should perhaps be a documented way to retain ownership in every environment; so that at least the environment system administrator can use the UI to manage solutions in cases of some urgent issue.
I work around this by importing the solution into the environments manually the first time, (as system administrator /customizer), then whenever ALM deploys a new version of the solution the ownership is retained. Perhaps this can be a solution for you as well?
I am having same issue as well - using Azure DevOp to migrate my app from Dev to Test environment and cannot share the app. Could you please elaborate on how the limitations have been addressed?
Hello @DeviKrishna ,
Regarding your second point. In this case, changing the ownership of an app and sharing it with users should be done with a ps script? If using an SPN is a recommended approach.
Thanks,
Anna
Hi @vammers ,
Looks like these limitations are addressed now from the time you created this ticket.
-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
My Blog: Dynamics 365 Key Topics – https://d365topicsbydk.com/
My YouTube Channel : https://www.youtube.com/channel/UCxSIryP2ah2VpEFr-Z72t1A
Regards
Devi
Hi guys,
I'm facing a similar issue too.
Can the command below be added to the pipeline files for importing?
Set-AdminPowerAppOwner -AppName $app.AppName -EnvironmentName $environmentName -AppOwner $Global:currentSession.userId
Share
Report
All responses (
Answers (
