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: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,11 +73,11 @@ QUICK DEPLOY
73
73
74
74
|[](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)|
75
75
|---|---|
76
-
[Steps to deploy with GitHub Codespaces](docs/DeployViaCodeSpaces.md)
76
+
[Steps to deploy with GitHub Codespaces](docs/github_code_spaces_steps.md)
77
77
78
78
79
79
## Connect to and validate access to the new environment
80
-
Follow the post deployment steps [Post Deployment Steps](docs/post_deployment_steps.md) to connect to the isolated environment.
80
+
Follow the post deployment steps [Post Deployment Steps](docs/github_code_spaces_steps.md) to connect to the isolated environment.
81
81
82
82
83
83
## Deploy your application in the isolated environment
Copy file name to clipboardExpand all lines: docs/github_code_spaces_steps.md
+22-22Lines changed: 22 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,43 +17,43 @@ You can run this solution using GitHub Codespaces. The button will open a web-ba
17
17
3. Click the Codespaces tab
18
18
4. Click "Create Codespaces on main"
19
19
20
-
20
+
21
21
22
22
This step will create the codespaces environment for you and launch a web based VS Code session.
23
23
5. In the terminal window (usually below by default) you can select the layout of the window in the upper right corner.
24
24
25
-
25
+
26
26
27
27
6. Log into your Azure subscription by leveraging the “azd auth login” command. Type the command “azd auth login”. It will display a code to copy and paste into the authorization window that will appear when you hit the enter button.
28
28
29
-
29
+
30
30
31
-
31
+
32
32
33
-
33
+
34
34
35
35
**Prompting for MFA**
36
36
37
-
37
+
38
38
39
39
7. Return to the codespaces window now. In the terminal window, begin by initializing the environment by typing the command “azd init”
40
40
41
-
41
+
42
42
43
43
8. Enter the name for your environment
44
44
45
-
45
+
46
46
47
47
9. Now start the deployment of the infrastructure by typing the command “azd provision”
48
48
49
-
49
+
50
50
51
51
This step will allow you to choose from the subscriptions you have available, based on the account you logged in with in the azd auth login step. Next it will prompt you for the region to deploy the resources into.
52
52
53
-
53
+
54
54
55
55
10. Next you will be prompted for values to enable additional features outside of the AI Foundry required features. They are false by default.
56
-
56
+
57
57
**Be sure to remember the vm password and vm username. This will be used in a later step. Because we are using FDPO subscriptions, we do not have access to Entra to create the SSO to the jump box at this time. You are still required to log into Azure once you connect to the virtual machine.
58
58
59
59
11. After completeing the required paramters that you were prompted for, the provisioning of resources will run and deploy the Network Isolated AI hub, project and dependent resources in about 20 minutes.
@@ -64,58 +64,58 @@ Follow these steps to check the creation of the required private endpoints in th
64
64
65
65
One way to check if the access is private to the hub is to launch the AI Foundry hub from the portal.
66
66
67
-
67
+
68
68
69
69
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!
70
70
71
-
71
+
72
72
73
73
A more thourough check is to look for the networking settings and checking for private end points.
74
74
75
75
1. Go to the Azure Portal and select your Azure AI hub that was just created.
76
76
77
77
2. Click on Settings and then Networking.
78
78
79
-
79
+
80
80
81
81
3. Open the Workspace managed outbound access tab.
82
82
83
-
83
+
84
84
85
85
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.
86
86
The hub should show that Public access is ‘disabled’.
87
87
88
88
## Connecting to the isolated network via RDP
89
89
1. Navigate to the resource group where the isolated AI Foundry was deployed to and select the virtual machine.
90
90
91
-
91
+
92
92
93
93
2. Be sure that the Virtual Machine is running. If not, start the VM.
94
94
95
-
95
+
96
96
97
97
3. Select “Bastion” under the ‘Connect’ heading in the VM resource.
98
98
99
-
99
+
100
100
101
101
4. Supply the username and the password you created as environment variables and press the connect button.
102
102
103
-
103
+
104
104
105
105
5. Your virtual machine will launch and you will see a different screen.
106
106
107
-
107
+
108
108
109
109
6. Launch Edge browser and navigate to your AI Foundry Hub. https://ai.azure.com Sign in using your credentials.
110
110
111
111
112
112
7. You are challenged by MFA to connect.
113
113
114
-
114
+
115
115
116
116
8. You will now be able to view the Foundry Hub which is contained in an isolated network.
117
117
118
-
118
+
0 commit comments