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 architecture will be deployed with the 'sandbox' setting of our deployment process. Optionally you can deploy [Well-Architected Framework (WAF) aligned](https://learn.microsoft.com/en-us/azure/well-architected/) architecture, described in [WAF-Aligned Solution Architecture](./docs/ArchitectureWAF.md), with the WAF-Aligned deployment option described in [Deployment Guide](./docs/DeploymentGuide.md).
@@ -51,16 +54,16 @@ If you'd like to customize the solution accelerator, here are some common areas
51
54
<summary>Click to learn more about the key features this solution enables</summary>
52
55
53
56
-**Code language modernization** <br/>
54
-
Modernizing outdated code ensures compatibility with current technologies, reduces reliance on legacy expertise, and keeps businesses competitive.
57
+
Modernizing outdated code ensures compatibility with current technologies, reduces reliance on legacy expertise, and keeps businesses competitive.
55
58
56
59
-**Summary and review of new code** <br/>
57
-
Generating summaries and translating code files keeps humans in the loop, enhances their understanding, and facilitates timely interventions, ensuring the files are ready to export.
60
+
Generating summaries and translating code files keeps humans in the loop, enhances their understanding, and facilitates timely interventions, ensuring the files are ready to export.
58
61
59
62
-**Business logic analysis** <br/>
60
-
Leveraging AI to decipher business logic from legacy code helps minimizes the risk of human error.
63
+
Leveraging AI to decipher business logic from legacy code helps minimizes the risk of human error.
61
64
62
65
-**Efficient code transformation** <br/>
63
-
Streamlining the process of analyzing, converting, and iterative error testing reduces time and effort required to modernize the systems.
66
+
Streamlining the process of analyzing, converting, and iterative error testing reduces time and effort required to modernize the systems.
64
67
65
68
</details>
66
69
@@ -77,7 +80,7 @@ Follow the quick deploy steps on the deployment guide to deploy this solution to
77
80
78
81
|[](https://codespaces.new/microsoft/Modernize-your-Code-Solution-Accelerator)|[](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/Modernize-your-Code-Solution-Accelerator)|
This architecture implements [Azure Well-Architected Framework (WAF)](https://learn.microsoft.com/en-us/azure/well-architected/) principles for enterprise-grade deployments, deployed with the WAF-Aligned deployment option:
-**Configurable Parameters:** If user selects to deploy as WAF Aligned, Parameters like Monitoring, Scaling, VPN will get enabled.
46
+
-**Network-first Design:** All components deployed within private network boundaries
47
+
-**Enterprise-ready:** Production-grade security and monitoring enabled
48
+
49
+
## Application Information Flow
50
+
51
+
The application information flow remains the same for both 'sandbox' and 'waf-aligned' configuration.
52
+
53
+
The solution is composed of several services:
54
+
55
+
- The web app front end and the backend app logic are containerized and run from Azure Container service instances.
56
+
- When a request for conversion is created in the web app admin console, the user specifies what files should be converted and the target SQL dialect for conversion.
57
+
- These files are then uploaded to blob storage and initial data about the request is stored in Cosmos DB.
58
+
- The conversion takes place using appropriate LLM models using multiple agents, with each agent having a dedicated purpose in the conversion process. As files are converted, they are placed into blob storage, with metadata collected into Cosmos detailing the conversion process and the current state of the batch.
59
+
- Cosmos also stores the logs from the individual agents so the results can be fully reviewed before any of the converted files are put into production.
Copy file name to clipboardExpand all lines: docs/DeploymentGuide.md
+41-10Lines changed: 41 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Check the [Azure Products by Region](https://azure.microsoft.com/en-us/explore/g
31
31
32
32
|[](https://codespaces.new/microsoft/Modernize-your-Code-Solution-Accelerator)|[](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/Modernize-your-Code-Solution-Accelerator)|
33
33
|---|---|
34
-
34
+
35
35
### **Configurable Deployment Settings**
36
36
37
37
When you start the deployment, most parameters will have **default values**, but you can update the following settings by following the steps [here](../docs/CustomizingAzdParameters.md):
@@ -61,7 +61,33 @@ By default, the **GPT model capacity** in deployment is set to **5k tokens**.
61
61
62
62
To adjust quota settings, follow these [steps](../docs/AzureGPTQuotaSettings.md)
63
63
64
-
### Deployment Options
64
+
### Deployment Options & Steps
65
+
### Sandbox or WAF Aligned Deployment Options
66
+
67
+
The [`infra`](../infra) folder contains the [`main.bicep`](../infra/main.bicep) Bicep script, which defines all Azure infrastructure components for this solution.
68
+
69
+
When running `azd up`, you’ll now be prompted to choose between a **WAF-aligned configuration** and a **sandbox configuration** using a simple selection:
70
+
71
+
- A **sandbox environment** — ideal for development and proof-of-concept scenarios, with minimal security and cost controls for rapid iteration.
72
+
73
+
- A **production deployments environment**, 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:
74
+
- Enhanced network security (e.g., Network protection with private endpoints)
75
+
- Stricter access controls and managed identities
76
+
- Logging, monitoring, and diagnostics enabled by default
77
+
- Resource tagging and cost management recommendations
- Select **`true`** to deploy a **WAF-aligned, production-ready environment**
86
+
- Select **`false`** to deploy a **lightweight sandbox/dev environment**
87
+
-
88
+
> [!TIP]
89
+
> 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.
90
+
65
91
Pick from the options below to see step-by-step instructions for: GitHub Codespaces, VS Code Dev Containers, Local Environments, and Bicep deployments.
66
92
67
93
<details>
@@ -133,23 +159,28 @@ To change the azd parameters from the default values, follow the steps [here](..
133
159
134
160
1. Login to Azure:
135
161
136
-
```shell
137
-
azd auth login
138
-
```
162
+
```shell
163
+
azd auth login
164
+
```
165
+
166
+
#### Note: To authenticate with Azure Developer CLI (`azd`) to a specific tenant, use the previous command with your **Tenant ID**:
167
+
168
+
```sh
169
+
azd auth login --tenant-id <tenant-id>
170
+
```
139
171
140
-
#### Note: To authenticate with Azure Developer CLI (`azd`) to a specific tenant, use the previous command with your **Tenant ID**:
172
+
2. Provide an `azd` environment name (like "cmsaapp")
141
173
142
-
```sh
143
-
azd auth login --tenant-id <tenant-id>
174
+
```sh
175
+
azd env new <cmsaapp>
144
176
```
145
177
146
-
2. Provision and deploy all the resources:
178
+
3. Provision and deploy all the resources:
147
179
148
180
```shell
149
181
azd up
150
182
```
151
183
152
-
3. Provide an `azd` environment name (like "cmsaapp")
153
184
4. Select a subscription from your Azure account, and select a location which has quota for all the resources.
154
185
* This deployment will take *6-9 minutes* to provision the resources in your account and set up the solution with sample data.
155
186
* If you get an error or timeout with deployment, changing the location can help, as there may be availability constraints for the resources.
0 commit comments