How to execute, "m365 spo list webhook add [options]" in Powershell?

[KANNIBALAMK]

How to execute these comments using Powershell to make it automated as part of CI CD?

[arjunumenon]

Hey @KANNIBALAMK - Can we ask what scenarios / setup are you trying to implement the CI/CD scenarios.

CLI does have GitHub Actions which you can use if you are using GitHub.

Otherwise if you are using any other Devops setup, CLI does allow you to login non-interactively as well (For e.g., via a Certificate) which you can refer from THIS LINK.

Let us know if that helps you out.

[KANNIBALAMK]

Hi I'm looking for a solution to add Azure function Url as a webhook to SharePoint document library.. So I need to run CLI to add webhook.. Looking for CI CD approach, since I need to add webhook to respective SharePoint Environment ( DEV/TST/ACC/PRD).. Thanks and regards Kannibala

…

On Thu, Aug 11, 2022, 7:40 PM Arjun Menon ***@***.***> wrote: Hey @KANNIBALAMK <https://github.com/KANNIBALAMK> - Can we ask what scenarios / setup are you trying to implement the CI/CD scenarios. CLI do have GitHub Actions <https://pnp.github.io/cli-microsoft365/user-guide/github-actions/> which you can use if you are using GitHub. Otherwise if you are using any other Devops setup, CLI does allow you to login non-interactively as well (For e.g., via a Certificate) which you can refer from THIS LINK <https://pnp.github.io/cli-microsoft365/user-guide/connecting-office-365/#log-in-using-a-certificate> . Let us know if that helps you out. — Reply to this email directly, view it on GitHub <#3573 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2OFCUDNDNWN62QYVUNB5VDVYUCV3ANCNFSM56D5HS3A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[arjunumenon]

Thanks for the response and giving the details. Based on your case, here is what the approach would be in my opinion.

1. Configure and Login to CLI using your Azure AD Identity
2. Login to the M365 using your own Identity and by non-interactive way either by Certificate approach or by Client Secret Approach
3. Then execute the command to add your URL to the webhook using m365 spo list webhook

In your case, Steps 1-3 need to be repeated in all the SharePoint environment which you mentioned which could be configured in CI/CD setup in any Devops environment. Hope that helps.

[KANNIBALAMK]

Hi Arjun Below things are fine. But I'm looking for a solution to automate it through YAML. I need to get the siteurl, List name and webhook url dynamically from parameter file and pass those parameters to powershell.

…

On Thu, Aug 11, 2022, 8:29 PM Arjun Menon ***@***.***> wrote: Thanks for the response and giving the details. Based on your case, here is what the approach would be in my opinion. 1. Configure and Login to CLI using your Azure AD Identity <https://pnp.github.io/cli-microsoft365/user-guide/using-own-identity/#use-your-own-azure-ad-identity> 2. Login to the M365 using your own Identity and by non-interactive way either by Certificate approach <https://pnp.github.io/cli-microsoft365/user-guide/connecting-office-365/#log-in-using-a-certificate> or by Client Secret Approach <https://pnp.github.io/cli-microsoft365/user-guide/connecting-office-365/#log-in-using-a-secret> 3. Then execute the command to add your URL to the webhook using m365 spo list webhook <https://pnp.github.io/cli-microsoft365/cmd/spo/list/list-webhook-add/> In your case, Steps 1-3 need to be repeated in all the SharePoint environment which you mentioned which could be configured in CI/CD setup in any Devops environment. Hope that helps. — Reply to this email directly, view it on GitHub <#3573 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2OFCUCYCP4UWAUVHVGYSRDVYUIMXANCNFSM56D5HS3A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[arjunumenon]

Typically this is done by keeping SharePoint related information as variables in the release pipeline.
You can refer to THIS link where it has shown how to deploy SPFx solutions to SharePoint.

In your case instead of App Catalog URL you can keep your SharePoint's List URL in the variable