🎯 Aim
We have a nice guide on how to use CLI for M365 in GitHub workflows but it's not the only DevOps environment where we may use CLI.
The idea is to add guidance how we may use CLI in Azure DevOps. We should definitely include:
👍 Additionally
In the GitHub workflow setup guide, we have 'Creating a basic workflow which authenticates with an Microsoft 365 tenant' section which explains how to create a basic workflow using CLI to deploy a SPFx package.
https://pnp.github.io/cli-microsoft365/user-guide/github-actions#creating-a-basic-workflow-which-authenticates-with-an-microsoft-365-tenant
Actually, now we have a command that will generate that for the user 🙂. Along the way we could include this info in the guide as well 👍
🎯 Aim
We have a nice guide on how to use CLI for M365 in GitHub workflows but it's not the only DevOps environment where we may use CLI.
The idea is to add guidance how we may use CLI in Azure DevOps. We should definitely include:
passwordone but rather go as a app)spfx project azuredevops pipeline addcommand which is currently a open PR so we could wait for it to be merged before we start working on this guide👍 Additionally
In the GitHub workflow setup guide, we have 'Creating a basic workflow which authenticates with an Microsoft 365 tenant' section which explains how to create a basic workflow using CLI to deploy a SPFx package.
https://pnp.github.io/cli-microsoft365/user-guide/github-actions#creating-a-basic-workflow-which-authenticates-with-an-microsoft-365-tenant
Actually, now we have a command that will generate that for the user 🙂. Along the way we could include this info in the guide as well 👍