Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
3 changes: 3 additions & 0 deletions docs/DeploymentGuide.md
Original file line number Diff line number Diff line change
Expand Up @@ -244,6 +244,9 @@ There are several ways to deploy the solution. You can deploy to run in Azure in

When Deployment is complete, follow steps in [Set Up Authentication in Azure App Service](../docs/azure_app_service_auth_setup.md) to add app authentication to your web app running on Azure App Service

### 🛠️ Troubleshooting
If you encounter any issues during the deployment process, please refer [troubleshoot](../docs/Troubleshoot.md) document for detailed steps and solutions.

# Local setup

> **Note for macOS Developers**: If you are using macOS on Apple Silicon (ARM64) the DevContainer will **not** work. This is due to a limitation with the Azure Functions Core Tools (see [here](https://github.com/Azure/azure-functions-core-tools/issues/3112)).
Expand Down
50 changes: 50 additions & 0 deletions docs/Troubleshoot.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
# 🛠️ Troubleshooting

## Enable `AllowBringYourOwnPublicIpAddress` Feature

Before deploying the resources, you may need to enable the **Bring Your Own Public IP Address** feature in Azure. This is required only once per subscription.

### Steps

1. **Run the following command to register the feature:**

```bash
az feature register --namespace Microsoft.Network --name AllowBringYourOwnPublicIpAddress
```

2. **Wait for the registration to complete.**
You can check the status using:

```bash
az feature show --namespace Microsoft.Network --name AllowBringYourOwnPublicIpAddress --query properties.state
```

3. **The output should show:**
"Registered"

4. **Once the feature is registered, refresh the provider:**

```bash
az provider register --namespace Microsoft.Network
```

Copy link

Copilot AI Aug 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code block is missing a closing backtick. Add ``` on a new line after the command to properly close the code block.

Suggested change
```

Copilot uses AI. Check for mistakes.
💡 Note: Feature registration may take several minutes to complete. This needs to be done only once per Azure subscription.

## Steps to avoid `ResourceGroupNotFound` Error

Before starting the deployment, ensure that the target resource group exists in your Azure subscription. Here are the steps to verify.

### Steps

1. Go to [Azure Portal](https:/portal.azure.com/#home).
Copy link

Copilot AI Aug 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Azure Portal URL is missing a slash. It should be 'https://portal.azure.com/#home' instead of 'https:/portal.azure.com/#home'.

Suggested change
1. Go to [Azure Portal](https:/portal.azure.com/#home).
1. Go to [Azure Portal](https://portal.azure.com/#home).

Copilot uses AI. Check for mistakes.

2. Click on the **"Resource groups"** option available on the Azure portal home page.
![alt text](../docs/images/AzureHomePage.png)


3. In the Resource Groups search bar, search for the resource group you intend to target for deployment. If it exists, you can proceed with using it.
![alt text](../docs/images/resourcegroup1.png)

💡 Note: If you encounter any other issues, please feel free to reach out to us. Thank you!


Binary file added docs/images/AzureHomePage.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/resourcegroup1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading