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
- Provides the ability to [add additional Azure services during deployment](docs/add_additional_services.md), configured to connect via isolation to enrich your AI project.
39
+
(API Management, CosmosDB, Azure SQL DB)
40
40
41
41
## Prerequisites and high-level steps
42
42
43
43
1. Have access to an Azure subscription and Entra ID account with Contributor permissions.
44
-
2. Confirm the subscription you are deploying into has the [Required Roles and Scopes](Required_roles_scopes_resources.md) and
45
-
3. If deploying from your [local environment](local_environment_steps.md) Install the [Azure Developer CLI (AZD)](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/install-azd?tabs=winget-windows%2Cbrew-mac%2Cscript-linux&pivots=os-windows)
46
-
4. If deploying via [GitHub Codespaces](github_code_spaces_steps.md) - requires the user to be on a GitHub Team or Enterprise Cloud plan
47
-
5. If leveraging [One-click deployment](#quick-deploy)
48
-
6. If leveraging [GitHub Actions](github_actions_steps.md)
44
+
2. Confirm the subscription you are deploying into has the [Required Roles and Scopes](docs/Required_roles_scopes_resources.md).
45
+
3. The solution ensures secure access to the private VNET through a jump-box VM with Azure Bastion. By default, Bastion does not require an inbound NSG rule for network traffic. However, if your environment enforces specific policy rules, you can resolve access issues by entering your machine's IP address in the `allowedIpAddress` parameter when prompted during deployment. If not specified, all IP addresses are allowed to connect to Azure Bastion.
46
+
4. If deploying from your [local environment](docs/local_environment_steps.md), install the [Azure Developer CLI (AZD)](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/install-azd?tabs=winget-windows%2Cbrew-mac%2Cscript-linux&pivots=os-windows).
47
+
5. If deploying via [GitHub Codespaces](docs/github_code_spaces_steps.md) - requires the user to be on a GitHub Team or Enterprise Cloud plan.
48
+
6. If leveraging [One-click deployment](#quick-deploy).
49
+
7. If leveraging [GitHub Actions](docs/github_actions_steps.md).
49
50
50
51
For additional documentation of the default enabled services of this solution accelerator, please see:
51
52
@@ -69,13 +70,13 @@ For additional documentation of the default enabled services of this solution ac
69
70
QUICK DEPLOY
70
71
</h2>
71
72
72
-
|[](https://codespaces.new/microsoft/Deploy-Your-AI-Application-In-Production)|[](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/Deploy-Your-AI-Application-In-Production)|[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmicrosoft%2FDeploy-Your-AI-Application-In-Production%2Fmain%2Finfra%2Fmain.json)|
73
-
|---|---|---|
74
-
[Steps to deploy with GitHub Codespaces](DeployViaCodeSpaces.md)
73
+
|[](https://codespaces.new/microsoft/Deploy-Your-AI-Application-In-Production)|[](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/Deploy-Your-AI-Application-In-Production)|
74
+
|---|---|
75
+
[Steps to deploy with GitHub Codespaces](docs/DeployViaCodeSpaces.md)
75
76
76
77
77
78
## Connect to and validate access to the new environment
78
-
Follow the post deployment steps [Post Deployment Steps](post_deployment_steps.md) to connect to the isolated environment.
79
+
Follow the post deployment steps [Post Deployment Steps](docs/post_deployment_steps.md) to connect to the isolated environment.
79
80
80
81
81
82
## Deploy your application in the isolated environment
Within this deployment automation of AI Foundry, we also have coupled several additional Azure services that are commonly deployed when creating an AI solution. We have added the ability to deploy these services at the same time as the AI Foundry deployment, or to add the services later.
4
+
These 'feature flags' leverage true/false values to either enable or disable (default behavior) the deployment and configuration of the following service(s):
5
+
6
+
**Table of the available feature flags in this repository:**
7
+
8
+
|**Feature Flag Name**|**Effect When Enabled**|**Instructions to Enable**|
|`cosmosDbEnabled`| Enables Cosmos DB integration. | Set the environment variable `AZURE_COSMOS_DB_ENABLED` to `true`. |
11
+
|`sqlServerEnabled`| Enables SQL Server integration. | Set the environment variable `AZURE_SQL_SERVER_ENABLED` to `true`. |
12
+
|`acrEnabled`| Enables Azure Container Registry (ACR) integration. | Set the environment variable `AZURE_ACR_ENABLED` to `true`. |
13
+
|`apiManagementEnabled`| Enables API Management integration. | Set the environment variable `AZURE_API_MANAGEMENT_ENABLED` to `true`. |
14
+
15
+
To enable these features during the deployment of your Foundry services, simply set the value to 'true' when prompted. This will add the selected feature during deployment, integrating it with the virtual network, private endpoints, and DNS zones.
16
+
You can set the values as an env variable within the code
17
+
```powershell
18
+
azd env set AZURE_API_MANAGEMENT_ENABLED true
19
+
```
20
+
21
+
Additionally, within the infra/ folder you can modify the main.parameters.json file to set the value to true by default.
0 commit comments