Azure DevOps Pipeline for Power Apps
Vložit
- čas přidán 28. 07. 2024
- Create an Azure Active Directory App Registration for Power Apps.
Use that App Registration to allow Azure DevOps to connect to your Power apps environment and add an application user using the Application ID in Azure.
Create an Azure Pipeline and add the service connection with the Power Apps server URL, Tenant ID, Client ID, and Secret ID. - Věda a technologie
Thank you so much for these steps!
Hi Andrea, great course! quick question, in the last step of the pipeline for the Command Line. You specified a "$(System.AccessToken)". Do I need to set this up somewhere? if so, can you advise how to setup? Thanks!
Great video!
Hey, what is the use of application user account that you have created. I saw it has not been referenced any where..can you help me to clarify on this please.
Thank you so much
Great video
Hi Andrea, Thank You the video. I have a question, in this approach as a last step, to check-in the exported solution, it will be always checked-in by a single mentioned user ?
Hello Andrea, Thanks for the great videos, I have done Dev to prod and testing using a similar approach, just want to understand if is there any option from one tenant to another tenant migration using the CI-CD pipeline? Thanks in Advance!.
Hi Andrea, I am a newbie to Azure DevOps but I have a question for you. Will this work if you don't use Dataverse but store you content in SharePoint??
Hi Christer, thanks for question. Yes ADO pipelines should be able to support your SharePoint data.
Hi Andrea, great video. About the app registration, do we actually need admin consent if the permissions are just delegated and "Admin consent required" is set to no? that would save me some time towards my GlobalAdmins...thanks!
Hello! I would double check with your organization.
@@andreapinillos thanks! I tested without the flag, it's actually working in devops. I moved the pipeline to YAML so I could enter parameters to support the "managed/unmanaged" scenario, the export of the solution and the connection to source and target environment. I was wondering what is the best practice once I want to use this pipeline for multiple apps. Is it ok to have all of them in the same repo, different folder? The commit message I use is reflects the name of the solution the managed/unmanged, the target and source environment plus the build number.
Nice video but
Why my whole pipeline fails? i have done everything as shown in video....
Hi Andrea. Great video however you sound is so faint in some parts of the video. Thanks
Will it work for SQL Server connection for both test and prod ?
Yes
I'm sys admin/customizer but still can't see that view for application users. Any suggestions? Let me know please. thanks
In this part of the video: czcams.com/video/wdMjx16JEG8/video.html, instead of clicking See all users, click S2S apps. That is another way to add application users.
@@danielpenrod6472 ahh got past this step now. Thanks! :)