From 8a6332452835f805d42a3f087656ce929a24d0b7 Mon Sep 17 00:00:00 2001 From: Milan Holemans <11723921+milanholemans@users.noreply.github.com> Date: Mon, 3 Feb 2025 15:39:34 +0100 Subject: [PATCH] Applies code review --- docs/docs/user-guide/automation/azure-function-powershell.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/user-guide/automation/azure-function-powershell.mdx b/docs/docs/user-guide/automation/azure-function-powershell.mdx index ebd1b0bbc56..a8ff4fd3890 100644 --- a/docs/docs/user-guide/automation/azure-function-powershell.mdx +++ b/docs/docs/user-guide/automation/azure-function-powershell.mdx @@ -83,7 +83,7 @@ Apart from this IDE, you will need the following extensions for Visual Studio Co 1. Create `package.json` file in the root of the project. - To use CLI for Microsoft 365 in this Azure Function, we have to install it locally in the project. When everything is ready to go, we will publish CLI for Microsoft 365 with out code to the Azure Function. + To use CLI for Microsoft 365 in this Azure Function, we have to install it locally in the project. When everything is ready to go, we will publish CLI for Microsoft 365 with our own code to the Azure Function. This will prevent the need to install the CLI for Microsoft 365 on the Azure Function itself at every execution. The easiest way to achieve this is to create a `package.json` file in the root of your project (or run `npm init`). Make sure your file looks like this (choose your own project name and version):