Community forums
Azure DevOps: using client id/secret to deploy
Quote from Scott Kearney on July 23, 2019, 11:07 amDo you want to use Azure Devops for deployments, but do not want to use a username/password? Try using a client id/secret instead.
NOTE: This would be the preferred method for enterprise deployments to not worry about a password expiring or if you are using MFA for users.
You can setup a build pipeline and use the parameters from here: https://github.com/akumina/AkuminaDev/tree/master/SiteDeployer/4100
clientid
Sharepoint app client id guid clientsecret
Sharepoint app client secret
As long as the SharePoint app allows App Only access, you can then run the pipeline and have it deploy the artifacts.
Some more reading:
Azure DevOps: Setting up a build to deploy a site package:
https://github.com/akumina/AkuminaDev/wiki/Azure-DevOps:-Setting-up-a-build-to-deploy-a-site-package
Assigning App Only permissions to a sharepoint app:
Do you want to use Azure Devops for deployments, but do not want to use a username/password? Try using a client id/secret instead.
NOTE: This would be the preferred method for enterprise deployments to not worry about a password expiring or if you are using MFA for users.
You can setup a build pipeline and use the parameters from here: https://github.com/akumina/AkuminaDev/tree/master/SiteDeployer/4100
clientid |
Sharepoint app client id | guid |
clientsecret |
Sharepoint app client secret |
As long as the SharePoint app allows App Only access, you can then run the pipeline and have it deploy the artifacts.
Some more reading:
Azure DevOps: Setting up a build to deploy a site package:
https://github.com/akumina/AkuminaDev/wiki/Azure-DevOps:-Setting-up-a-build-to-deploy-a-site-package
Assigning App Only permissions to a sharepoint app: