Skip to content

Updated the pre-requisite section with (optional) step to avoid bicep runtime download error while using azd up #202

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ponarunkumar wants to merge 2 commits into
base: main
Choose a base branch
from
+12 −0
Open

Updated the pre-requisite section with (optional) step to avoid bicep runtime download error while using azd up #202

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
87dab47
Added (Optional) Pre-requisite Section for installing bicep to avoid …
ponarunkumar Dec 2, 2025
a9bf177
updated the pre-requisites section with (optional) step to avoid any …
ponarunkumar Dec 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,18 @@ Check the [Azure Products by Region](https://azure.microsoft.com/explore/global-

Here are some examples of the regions where the services are available: East US, East US2, Japan East, UK South, Sweden Central.

### Install and verify the Bicep CLI

`azd up` compiles every file under `infra/*.bicep`. To avoid network downloads during deployment, make sure the Bicep CLI is already available on your machine (or Codespace) through the Azure CLI:

```bash
az bicep install # or az bicep upgrade
az bicep version # verify installation
```

If you prefer to use the standalone `bicep` binary, place it on your `PATH` before running `azd up`.


### **Important Note for PowerShell Users**

If you encounter issues running PowerShell scripts due to the policy of not being digitally signed, you can temporarily adjust the `ExecutionPolicy` by running the following command in an elevated PowerShell session:
Expand Down