Skip to content

Commit fef5fd2

Browse files
committed
UI refresh
1 parent 84576c9 commit fef5fd2

File tree

10 files changed

+21
-24
lines changed

10 files changed

+21
-24
lines changed

articles/ai-studio/how-to/data-add.md

Lines changed: 16 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -66,18 +66,18 @@ These steps explain how to create a File typed data in Azure AI Studio:
6666

6767
1. Choose your **Data source**. You have three options to choose a data source.
6868
- You can select data from **Existing Connections**.
69-
- You can **Get data with Storage URL** if you have a direct URL to a storage account or a public accessible HTTPS server.
70-
- You can choose **Upload files/folders** to upload a folder from your local drive.
69+
- You can select **Get data with Storage URL** if you have a direct URL to a storage account or a public accessible HTTPS server.
70+
- You can select **Upload files/folders** to upload a folder from your local drive.
7171

7272
:::image type="content" source="../media/data-add/select-connection.png" alt-text="This screenshot shows the existing connections.":::
7373

74-
1. **Existing Connections**: You can select an existing connection, browse into this connection, and choose a file you need. If the existing connections don't work for you, select the **New connection** button at the upper right.
74+
- **Existing Connections**: You can select an existing connection, browse into this connection, and choose a file you need. If the existing connections don't work for you, select the **New connection** button at the upper right.
7575
:::image type="content" source="../media/data-add/new-connection.png" alt-text="This screenshot shows the creation of a new connection to an external asset.":::
7676

77-
1. **Get data with Storage URL**: You can choose the **Type** as "File", and then provide a URL based on the supported URL formats listed on that page.
77+
- **Get data with Storage URL**: You can choose the **Type** as "File", and then provide a URL based on the supported URL formats listed on that page.
7878
:::image type="content" source="../media/data-add/file-url.png" alt-text="This screenshot shows provision of a URL that points to a file.":::
7979

80-
1. **Upload files/folders**: You can select **Upload files or folder**, select **Upload files**, and choose the local file to upload. The file uploads into the default "workspaceblobstore" connection.
80+
- **Upload files/folders**: You can select **Upload files or folder**, select **Upload files**, and choose the local file to upload. The file uploads into the default "workspaceblobstore" connection.
8181
:::image type="content" source="../media/data-add/upload.png" alt-text="This screenshot shows the step to upload files/folders.":::
8282

8383
1. Select **Next** after you choose the data source.
@@ -103,15 +103,15 @@ A Folder (`uri_folder`) data source type points to a *folder* on a storage resou
103103

104104
:::image type="content" source="../media/data-add/select-connection.png" alt-text="This screenshot shows the existing connections.":::
105105

106-
1. **Existing Connections**: You can select an existing connection and browse into this connection and choose a file you need. If the existing connections don't work for you, you can select the **New connection** button at the right.
106+
- **Existing Connections**: You can select an existing connection and browse into this connection and choose a file you need. If the existing connections don't work for you, you can select the **New connection** button at the right.
107107

108108
:::image type="content" source="../media/data-add/choose-folder.png" alt-text="This screenshot shows the step to choose a folder from an existing connection.":::
109109

110-
1. **Get data with Storage URL**: You can choose the **Type** as "Folder", and provide a URL based on the supported URL formats listed on that page.
110+
- **Get data with Storage URL**: You can choose the **Type** as "Folder", and provide a URL based on the supported URL formats listed on that page.
111111

112112
:::image type="content" source="../media/data-add/folder-url.png" alt-text="This screenshot shows the step to provide a URL that points to a folder.":::
113113

114-
1. **Upload files/folders**: You can select **Upload files or folder**, and select **Upload files**, and choose the local file to upload. The file resources upload into the default "workspaceblobstore" connection.
114+
- **Upload files/folders**: You can select **Upload files or folder**, and select **Upload files**, and choose the local file to upload. The file resources upload into the default "workspaceblobstore" connection.
115115

116116
:::image type="content" source="../media/data-add/upload.png" alt-text="This screenshot shows the step to upload files/folders.":::
117117

@@ -126,20 +126,17 @@ A Folder (`uri_folder`) data source type points to a *folder* on a storage resou
126126
### Delete data
127127

128128
> [!IMPORTANT]
129-
> ***By design*, data deletion is not supported.**
130-
>
131-
> If Azure AI allowed data deletion, it would have the following adverse effects:
132-
>
133-
> - **Production jobs** that consume data that is later deleted would fail.
134-
> - ML experiment reproduction would become more difficult.
135-
> - Job **lineage** would break, because it would become impossible to view the deleted data version.
136-
> - You could no longer **track and audit** correctly, since versions could be missing.
137-
>
138-
> Therefore, data *immutability* provides a level of protection when working in a team that creates production workloads.
129+
> Data deletion is not supported. Data is immutable in AI Studio. Once you create a data version, it can't be modified or deleted. This immutability provides a level of protection when working in a team that creates production workloads.
130+
131+
If AI Studio allowed data deletion, it would have the following adverse effects:
132+
- Production jobs that consume data that is later deleted would fail.
133+
- Machine learning experiment reproduction would become more difficult.
134+
- Job lineage would break, because it would become impossible to view the deleted data version.
135+
- You could no longer track and audit correctly, since versions could be missing.
139136

140137
When a data resource is erroneously created - for example, with an incorrect name, type or path - Azure AI offers solutions to handle the situation without the negative consequences of deletion:
141138

142-
|*I want to delete this data because...* | Solution |
139+
|Reason that you might want to delete data | Solution |
143140
|---------|---------|
144141
|The **name** is incorrect | [Archive the data](#archive-data) |
145142
|The team **no longer uses** the data | [Archive the data](#archive-data) |

articles/ai-studio/how-to/deploy-models-llama.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ To create a deployment:
125125

126126
Alternatively, you can initiate deployment by starting from your project in AI Studio. Select a project and then select **Deployments** > **+ Create**.
127127

128-
1. On the model's **Details** page, select **Deploy** and then select **Pay-as-you-go**.
128+
1. On the model's **Details** page, select **Deploy** in the **Serverless APIs** section.
129129

130130
1. Select the project in which you want to deploy your models. To use the pay-as-you-go model deployment offering, your workspace must belong to the **East US 2** or **Sweden Central** region.
131131
1. On the deployment wizard, select the link to **Azure Marketplace Terms** to learn more about the terms of use. You can also select the **Marketplace offer details** tab to learn about pricing for the selected model.
@@ -157,16 +157,16 @@ To create a deployment:
157157

158158
Alternatively, you can initiate deployment by starting from your project in AI Studio. Select a project and then select **Deployments** > **+ Create**.
159159

160-
1. On the model's **Details** page, select **Deploy** and then select **Pay-as-you-go**.
160+
1. On the model's **Details** page, select **Deploy** in the **Serverless APIs** section.
161161

162162
:::image type="content" source="../media/deploy-monitor/llama/deploy-pay-as-you-go.png" alt-text="A screenshot showing how to deploy a model with the pay-as-you-go option." lightbox="../media/deploy-monitor/llama/deploy-pay-as-you-go.png":::
163163

164164
1. Select the project in which you want to deploy your models. To use the pay-as-you-go model deployment offering, your workspace must belong to the **East US 2** or **West US 3** region.
165165
1. On the deployment wizard, select the link to **Azure Marketplace Terms** to learn more about the terms of use. You can also select the **Marketplace offer details** tab to learn about pricing for the selected model.
166-
1. If this is your first time deploying the model in the project, you have to subscribe your project for the particular offering (for example, Meta-Llama-2-70B) from Azure Marketplace. This step requires that your account has the Azure subscription permissions and resource group permissions listed in the prerequisites. Each project has its own subscription to the particular Azure Marketplace offering, which allows you to control and monitor spending. Select **Subscribe and Deploy**.
166+
1. If this is your first time deploying the model in the project, you have to subscribe your project for the particular offering (for example, Meta-Llama-2-7B) from Azure Marketplace. This step requires that your account has the Azure subscription permissions and resource group permissions listed in the prerequisites. Each project has its own subscription to the particular Azure Marketplace offering, which allows you to control and monitor spending. Select **Subscribe and Deploy**.
167167

168168
> [!NOTE]
169-
> Subscribing a project to a particular Azure Marketplace offering (in this case, Meta-Llama-2-70B) requires that your account has **Contributor** or **Owner** access at the subscription level where the project is created. Alternatively, your user account can be assigned a custom role that has the Azure subscription permissions and resource group permissions listed in the [prerequisites](#prerequisites).
169+
> Subscribing a project to a particular Azure Marketplace offering (in this case, Meta-Llama-2-7B) requires that your account has **Contributor** or **Owner** access at the subscription level where the project is created. Alternatively, your user account can be assigned a custom role that has the Azure subscription permissions and resource group permissions listed in the [prerequisites](#prerequisites).
170170
171171
:::image type="content" source="../media/deploy-monitor/llama/deploy-marketplace-terms.png" alt-text="A screenshot showing the terms and conditions of a given model." lightbox="../media/deploy-monitor/llama/deploy-marketplace-terms.png":::
172172

@@ -493,7 +493,7 @@ Follow these steps to deploy a model such as `Llama-2-7b-chat` to a real-time en
493493

494494
Alternatively, you can initiate deployment by starting from your project in AI Studio. Select your project and then select **Deployments** > **+ Create**.
495495

496-
1. On the model's **Details** page, select **Deploy** and then **Real-time endpoint**.
496+
1. On the model's **Details** page, select **Deploy** next to the **View license** button.
497497

498498
:::image type="content" source="../media/deploy-monitor/llama/deploy-real-time-endpoint.png" alt-text="A screenshot showing how to deploy a model with the real-time endpoint option." lightbox="../media/deploy-monitor/llama/deploy-real-time-endpoint.png":::
499499

Binary file not shown.
67.7 KB
Loading
-3.93 KB
Loading
-144 KB
Loading
357 KB
Loading
642 KB
Loading
Binary file not shown.
Binary file not shown.

0 commit comments

Comments
 (0)