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
Copy file name to clipboardExpand all lines: docs/Dev_ContainerSteps.md
+31-18Lines changed: 31 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,19 +30,35 @@ You can run this solution in VS Code Dev Containers, which will open the project
30
30
The [Azure CLI](https://learn.microsoft.com/en-us/cli/azure/what-is-azure-cli?view=azure-cli-latest) is used to validate available AI model quota.
31
31
32
32

33
+
3. Return to terminal and type the below commandfor initializing the environment.
34
+
```shell
35
+
azd init
36
+
```
37
+

38
+
39
+
4. Enter the environment name.
40
+
>**Note:** Length of the environment name should be less than or equal to 12 characters.
41
+
42
+

33
43
34
-
3. Now start the deployment of the infrastructure by typing the below command:
44
+
5. Now start the deployment of the infrastructure by typing the below command:
35
45
```shell
36
46
azd up
37
47
```
38
48
> ⚠️ **Note:** The latest version of the Azure Developer CLI (AZD) is currently limited on prompting formissing parameters. The feature flag parametersin this solution have been temporarily defaulted to `'disabled'`until this limitation is lifted and prompting will resume.
39
49
40
50
41
-

42
-
51
+

52
+
Log in to **Azure**for authentication. 
43
53
This step will allow you to choose from the subscriptions you have available, based on the account you logged in with in the login step. Next it will prompt you for the region to deploy the resources into as well as any additional Azure resources to be provisioned and configured.
44
-
54
+
45
55
**Important:** Be sure to remember the vm password. This will be used in a later step. You are still required to log into Azure once you connect through the virtual machine.
56
+
> ⚠️ **Note:**
57
+
> 1. For **WAF Deployment**, Select the **Network Isolation** as **'True'**.
58
+
>
59
+
> 2. For **Sample App Deployment**, Select the **appSampleEnabled** as **'True'**.
60
+
>
61
+
46
62
47
63
6. The automated model quota check will run, and will check if the location selected will have the necessary quota forthe AI Models that are listedin the parameters file prior to deploying any resources.
48
64

@@ -63,28 +79,25 @@ You can run this solution in VS Code Dev Containers, which will open the project
63
79
These steps will help to check that the isolated environment was set up correctly.
64
80
Follow these steps to check the creation of the required private endpoints in the environment (when set to networkIsolation = true).
65
81
66
-
One way to check if the access is private to the hub is to launch the AI Foundry hub from the portal.
82
+
One way to verify whether access is private to the foundry is by launching Azure AI Foundry from the portal.
67
83
68
-

84
+

69
85
70
86
When a user that is not connected through the virtual network via an RDP approved connection will see the following screen in their browser. This is the intended behavior!
71
87
72
-

88
+

73
89
74
90
A more thourough check is to look for the networking settings and checking for private end points.
75
91
76
92
1. Go to the Azure Portal and selectyour Azure AI hub that was just created.
77
93
78
-
2. Click on Settings and then Networking.
79
-
80
-

94
+
2. Click on Resource Management and then Networking.
81
95
82
-
3. Open the Workspace managed outbound access tab.
96
+

83
97
84
-

85
98
86
-
Here, you will find the private endpoints that are connected to the resources within the hub managed virtual network. Ensure that these private endpoints are active.
87
-
The hub should show that Public access is ‘disabled’.
99
+
Here, you will find the private endpoints that are connected to the resources within the foundry managed virtual network. Ensure that these private endpoints are active.
100
+
The foundry should show that Public access is ‘disabled’.
88
101
89
102
## Connecting to the isolated network via RDP
90
103
1. Navigate to the resource group where the isolated AI Foundry was deployed to and selectthe virtual machine.
@@ -101,22 +114,22 @@ A more thourough check is to look for the networking settings and checking for p
101
114
102
115
4. Supply the username and the password you created as environment variables and press the connect button.
103
116
104
-

117
+

105
118
106
119
5. Your virtual machine will launch and you will see a different screen.
107
120
108
121

109
122
110
-
6. Launch Edge browser and navigate to your AI Foundry Hub. https://ai.azure.com Sign in using your credentials.
123
+
6. Launch Edge browser and navigate to your Azure AI Foundry. https://ai.azure.com Sign in using your credentials.
111
124
112
125
113
126
7. You are challenged by MFA to connect.
114
127
115
128

116
129
117
-
8. You will now be able to view the Foundry Hub which is contained in an isolated network.
130
+
8. You will now be able to view the Azure AI Foundry which is contained in an isolated network.
118
131
119
-

132
+

Copy file name to clipboardExpand all lines: docs/github_code_spaces_steps.md
+19-16Lines changed: 19 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,7 @@ You can run this solution using GitHub Codespaces. The button will open a web-ba
38
38

39
39
40
40
4. Enter the environment name.
41
+
>**Note:** Length of the environment name should be less than or equal to 12 characters.
41
42
42
43

43
44
@@ -47,11 +48,16 @@ You can run this solution using GitHub Codespaces. The button will open a web-ba
47
48
```
48
49
> ⚠️ **Note:** The latest version of the Azure Developer CLI (AZD) is currently limited on prompting formissing parameters. The feature flag parametersin this solution have been temporarily defaulted to `'disabled'`until this limitation is lifted and prompting will resume.
49
50
50
-

51
-
51
+

52
+
Log in to **Azure**for authentication. 
52
53
This step will allow you to choose from the subscriptions you have available, based on the account you logged in with in the login step. Next it will prompt you for the region to deploy the resources into as well as any additional Azure resources to be provisioned and configured.
53
54
54
55
**Important:** Be sure to remember the vm password. This will be used in a later step. You are still required to log into Azure once you connect through the virtual machine.
56
+
> ⚠️ **Note:**
57
+
> 1. For **WAF Deployment**, Select the **Network Isolation** as **'True'**.
58
+
>
59
+
> 2. For **Sample App Deployment**, Select the **appSampleEnabled** as **'True'**.
60
+
>
55
61
56
62
6. The automated model quota check will run, and will check if the location selected will have the necessary quota forthe AI Models that are listedin the parameters file prior to deploying any resources.
57
63

@@ -72,28 +78,25 @@ You can run this solution using GitHub Codespaces. The button will open a web-ba
72
78
These steps will help to check that the isolated environment was set up correctly.
73
79
Follow these steps to check the creation of the required private endpoints in the environment (when set to networkIsolation = true).
74
80
75
-
One way to check if the access is private to the hub is to launch the AI Foundry hub from the portal.
81
+
One way to verify whether access is private to the foundry is by launching Azure AI Foundry from the portal.
76
82
77
-

83
+

78
84
79
85
When a user that is not connected through the virtual network via an RDP approved connection will see the following screen in their browser. This is the intended behavior!
80
86
81
-

87
+

82
88
83
89
A more thourough check is to look for the networking settings and checking for private end points.
84
90
85
91
1. Go to the Azure Portal and selectyour Azure AI hub that was just created.
86
92
87
-
2. Click on Settings and then Networking.
88
-
89
-

93
+
2. Click on Resource Management and then Networking.
90
94
91
-
3. Open the Workspace managed outbound access tab.
95
+

92
96
93
-

94
97
95
-
Here, you will find the private endpoints that are connected to the resources within the hub managed virtual network. Ensure that these private endpoints are active.
96
-
The hub should show that Public access is ‘disabled’.
98
+
Here, you will find the private endpoints that are connected to the resources within the foundry managed virtual network. Ensure that these private endpoints are active.
99
+
The foundry should show that Public access is ‘disabled’.
97
100
98
101
## Connecting to the isolated network via RDP
99
102
1. Navigate to the resource group where the isolated AI Foundry was deployed to and selectthe virtual machine.
@@ -110,22 +113,22 @@ A more thourough check is to look for the networking settings and checking for p
110
113
111
114
4. Supply the username and the password you created as environment variables and press the connect button.
112
115
113
-

116
+

114
117
115
118
5. Your virtual machine will launch and you will see a different screen.
116
119
117
120

118
121
119
-
6. Launch Edge browser and navigate to your AI Foundry Hub. https://ai.azure.com Sign in using your credentials.
122
+
6. Launch Edge browser and navigate to your Azure AI Foundry. https://ai.azure.com Sign in using your credentials.
120
123
121
124
122
125
7. You are challenged by MFA to connect.
123
126
124
127

125
128
126
-
8. You will now be able to view the Foundry Hub which is contained in an isolated network.
129
+
8. You will now be able to view the Azure AI Foundry which is contained in an isolated network.
127
130
128
-

131
+

0 commit comments