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: articles/ai-services/language-service/conversational-language-understanding/concepts/best-practices.md
+11-16Lines changed: 11 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: nitinme
8
8
ms.service: cognitive-services
9
9
ms.subservice: language-service
10
10
ms.topic: best-practice
11
-
ms.date: 08/30/2023
11
+
ms.date: 09/22/2023
12
12
ms.author: aahi
13
13
ms.custom: language-service-clu
14
14
---
@@ -173,33 +173,28 @@ curl --request POST \
173
173
}'
174
174
```
175
175
176
-
## Best Practices for Copying Projects across language resources
176
+
## Copy projects across language resources
177
177
178
-
CLU projects can be easily copied from one resource to another using the Copy button in the UI. However in some cases, it might be easier to copy projects via the API. Here is how to do it.
178
+
Often you can copy conversational language understanding projects from one resource to another using the **copy** button in Azure Language Studio. However in some cases, it might be easier to copy projects using the API.
179
179
180
-
### Step 1
180
+
First, identify the:
181
+
* source project name
182
+
* target project name
183
+
* source language resource
184
+
* target language resource, which is where you want to copy it to.
181
185
182
-
Identify the
186
+
Call the API to authorize the copy action, and get the `accessTokens` for the actual copy operation later.
183
187
184
-
1. source-project-name
185
-
186
-
1. the target-project-name
187
-
188
-
1. the source-language-resource
189
-
190
-
1. the target-language-resource you want to copy it to. Call the authorize copy API as below to get the accessTokens for the actual Copy call (which is described in step 2)
0 commit comments