You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This guide provides step-by-step instructions to build and push Docker images for **WebApp** and **Backend** services into Azure Container Registry (ACR).
4
+
5
+
## 📋 Prerequisites
6
+
Before starting, ensure you have:
7
+
- An active [Azure Subscription](https://portal.azure.com/)
8
+
-[Azure CLI](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli) installed and logged in
9
+
-[Docker Desktop](https://docs.docker.com/get-docker/) installed and running
10
+
- Access to your Azure Container Registry (ACR)
11
+
- To create an Azure Container Registry (ACR), you can refer to the following guides:
12
+
13
+
-[Create Container Registry using Azure CLI](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-get-started-azure-cli)
14
+
15
+
-[Create Container Registry using Azure Portal](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal?tabs=azure-cli)
16
+
17
+
-[Create Container Registry using PowerShell](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-get-started-powershell)
18
+
19
+
-[Create Container Registry using ARM Template](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-get-started-geo-replication-template)
20
+
21
+
-[Create Container Registry using Bicep](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-get-started-bicep?tabs=CLI)
Copy file name to clipboardExpand all lines: documents/CustomizeData.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,3 +21,17 @@ If you would like to update the solution to leverage your own data please follow
21
21
```
22
22
a. resourcegroupname_param - the name of the resource group.
23
23
24
+
> Note (WAF‑aligned deployments): If you deployed the solution with the WAF / private networking option enabled, you must run the data processing script **from inside the deployed VM (jumpbox / processing VM)** so it can reach the private endpoints. Follow these steps:
25
+
>
26
+
> 1. Connect to the VM (Azure Bastion, SSH, or RDP depending on OS).
27
+
> 2. Ensure the repo (or the `infra/scripts` folder) is present. If not, clone or pull it.
28
+
> 3. Open a Bash-compatible shell (Git Bash on Windows, or native bash on Linux).
29
+
> 4. Run `az login` (add `--tenant <tenantId>`if required by your org policy).
Copy file name to clipboardExpand all lines: documents/CustomizingAzdParameters.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,13 @@ By default this template will use the environment name as the prefix to prevent
19
19
|`AZURE_OPENAI_API_VERSION`| string |`2025-01-01-preview`| Specifies the API version for Azure OpenAI. |
20
20
|`AZURE_OPENAI_DEPLOYMENT_MODEL_CAPACITY`| integer |`30`| Sets the GPT model capacity. |
21
21
|`AZURE_OPENAI_EMBEDDING_MODEL`| string |`text-embedding-ada-002`| Sets the name of the embedding model to use. |
22
-
|`AZURE_ENV_IMAGETAG`| string |`latest`| Sets the image tag (`latest`, `dev`, `hotfix`, etc.). |
22
+
|`AZURE_ENV_IMAGETAG`| string |`latest_waf`| Sets the image tag (`latest_waf`, `dev`, `hotfix`, etc.). |
23
23
|`AZURE_OPENAI_EMBEDDING_MODEL_CAPACITY`| integer |`80`| Sets the capacity for the embedding model deployment. |
24
24
|`AZURE_ENV_LOG_ANALYTICS_WORKSPACE_ID`| string | Guide to get your [Existing Workspace ID](/documents/re-use-log-analytics.md)| Reuses an existing Log Analytics Workspace instead of creating a new one. |
25
25
|`USE_LOCAL_BUILD`| string |`false`| Indicates whether to use a local container build for deployment. |
26
26
|`AZURE_EXISTING_AI_PROJECT_RESOURCE_ID`| string |`<Existing AI Project resource Id>`| Reuses an existing AIFoundry and AIFoundryProject instead of creating a new one. |
27
-
27
+
|`AZURE_ENV_VM_ADMIN_USERNAME`| string |`take(newGuid(), 20)`| The administrator username for the virtual machine. |
28
+
|`AZURE_ENV_VM_ADMIN_PASSWORD`| string |`newGuid()`| The administrator password for the virtual machine. |
Copy file name to clipboardExpand all lines: documents/DeploymentGuide.md
+41-2Lines changed: 41 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,45 @@ This will allow the scripts to run for the current session without permanently c
32
32
33
33
## Deployment Options & Steps
34
34
35
+
### Sandbox or WAF Aligned Deployment Options
36
+
37
+
The [`infra`](../infra) folder of the Multi Agent Solution Accelerator contains the [`main.bicep`](../infra/main.bicep) Bicep script, which defines all Azure infrastructure components for this solution.
38
+
39
+
By default, the `azd up` command uses the [`main.parameters.json`](../infra/main.parameters.json) file to deploy the solution. This file is pre-configured for a **sandbox environment** — ideal for development and proof-of-concept scenarios, with minimal security and cost controls for rapid iteration.
40
+
41
+
For **production deployments**, the repository also provides [`main.waf.parameters.json`](../infra/main.waf.parameters.json), which applies a [Well-Architected Framework (WAF) aligned](https://learn.microsoft.com/en-us/azure/well-architected/) configuration. This option enables additional Azure best practices for reliability, security, cost optimization, operational excellence, and performance efficiency, such as:
42
+
43
+
- Enhanced network security (e.g., Network protection with private endpoints)
44
+
- Stricter access controls and managed identities
45
+
- Logging, monitoring, and diagnostics enabled by default
46
+
- Resource tagging and cost management recommendations
47
+
48
+
**How to choose your deployment configuration:**
49
+
50
+
* Use the default `main.parameters.json` file for a **sandbox/dev environment**
51
+
* For a **WAF-aligned, production-ready deployment**, copy the contents of `main.waf.parameters.json` into `main.parameters.json` before running `azd up`
52
+
53
+
---
54
+
55
+
### VM Credentials Configuration
56
+
57
+
By default, the solution sets the VM administrator username and password from environment variables.
58
+
59
+
To set your own VM credentials before deployment, use:
60
+
61
+
```sh
62
+
azd env set AZURE_ENV_VM_ADMIN_USERNAME <your-username>
63
+
azd env set AZURE_ENV_VM_ADMIN_PASSWORD <your-password>
64
+
```
65
+
66
+
> [!TIP]
67
+
> Always review and adjust parameter values (such as region, capacity, security settings and log analytics workspace configuration) to match your organization’s requirements before deploying. For production, ensure you have sufficient quota and follow the principle of least privilege for all identities and role assignments.
68
+
69
+
> [!IMPORTANT]
70
+
> The WAF-aligned configuration is under active development. More Azure Well-Architected recommendations will be added in future updates.
71
+
72
+
### Deployment Steps
73
+
35
74
Pick from the options below to see step-by-step instructions for GitHub Codespaces, VS Code Dev Containers, Local Environments, and Bicep deployments.
36
75
37
76
|[](https://codespaces.new/microsoft/Conversation-Knowledge-Mining-Solution-Accelerator)|[](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/Conversation-Knowledge-Mining-Solution-Accelerator)|
@@ -80,7 +119,7 @@ If you're not using one of the above options for opening the project, then you'l
80
119
81
120
1. Make sure the following tools are installed:
82
121
-[PowerShell](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell?view=powershell-7.5) <small>(v7.0+)</small> - available for Windows, macOS, and Linux.
83
-
-[Azure Developer CLI (azd)](https://aka.ms/install-azd) <small>(v1.15.0+)</small> - version
122
+
-[Azure Developer CLI (azd)](https://aka.ms/install-azd) <small>(v1.18.0+)</small> - version
0 commit comments