Skip to content

Commit 15ef292

Browse files
updated waf steps in azd_deployment.md file
1 parent caf4be8 commit 15ef292

2 files changed

Lines changed: 18 additions & 34 deletions

File tree

content-gen/docs/AZD_DEPLOYMENT.md

Lines changed: 18 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -101,21 +101,28 @@ azd env set embeddingDeploymentCapacity 50
101101
azd env set azureOpenaiAPIVersion 2024-12-01-preview
102102
```
103103

104-
### 4. Enable Optional Features (WAF Pillars)
104+
### 4. Choose Deployment Configuration
105105

106-
```bash
107-
# Enable private networking (VNet integration)
108-
azd env set enablePrivateNetworking true
106+
The [`infra`](../infra) folder contains the [`main.bicep`](../infra/main.bicep) Bicep script, which defines all Azure infrastructure components for this solution.
109107

110-
# Enable monitoring (Log Analytics + App Insights)
111-
azd env set enableMonitoring true
108+
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**.
112109

113-
# Enable scalability (auto-scaling, higher SKUs)
114-
azd env set enableScalability true
110+
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 can be used for Production scenarios.
115111

116-
# Enable redundancy (zone redundancy, geo-replication)
117-
azd env set enableRedundancy true
118-
```
112+
**How to choose your deployment configuration:**
113+
114+
* **To use sandbox/dev environment** — Use the default `main.parameters.json` file.
115+
116+
* **To use production configuration:**
117+
118+
Before running `azd up`, copy the contents from the production configuration file to your main parameters file:
119+
120+
1. Navigate to the `infra` folder in your project.
121+
2. Open `main.waf.parameters.json` in a text editor (like Notepad, VS Code, etc.).
122+
3. Select all content (Ctrl+A) and copy it (Ctrl+C).
123+
4. Open `main.parameters.json` in the same text editor.
124+
5. Select all existing content (Ctrl+A) and paste the copied content (Ctrl+V).
125+
6. Save the file (Ctrl+S).
119126

120127
### 5. Deploy
121128

content-gen/docs/DEPLOYMENT.md

Lines changed: 0 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -161,29 +161,6 @@ Depending on your subscription quota and capacity, you can adjust quota settings
161161

162162
</details>
163163

164-
### Deployment Options
165-
166-
The [`infra`](../infra) folder of the Content Generation Solution Accelerator contains the [`main.bicep`](../infra/main.bicep) Bicep script, which defines all Azure infrastructure components for this solution.
167-
168-
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**.
169-
170-
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 can be used for Production scenarios.
171-
172-
**How to choose your deployment configuration:**
173-
174-
* **To use sandbox/dev environment** — Use the default `main.parameters.json` file.
175-
176-
* **To use production configuration:**
177-
178-
Before running `azd up`, copy the contents from the production configuration file to your main parameters file:
179-
180-
1. Navigate to the `infra` folder in your project.
181-
2. Open `main.waf.parameters.json` in a text editor (like Notepad, VS Code, etc.).
182-
3. Select all content (Ctrl+A) and copy it (Ctrl+C).
183-
4. Open `main.parameters.json` in the same text editor.
184-
5. Select all existing content (Ctrl+A) and paste the copied content (Ctrl+V).
185-
6. Save the file (Ctrl+S).
186-
187164
### Deploying with AZD
188165

189166
Once you've opened the project in [Codespaces](#github-codespaces), [Dev Containers](#vs-code-dev-containers), or [locally](#local-environment), you can deploy it to Azure by following the steps in the [AZD Deployment Guide](AZD_DEPLOYMENT.md).

0 commit comments

Comments
 (0)