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/cognitive-services/Translator/reference/v3-0-languages.md
+17-15Lines changed: 17 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.author: lajanuar
15
15
16
16
# Translator 3.0: Languages
17
17
18
-
Gets the set of languages currently supported by other operations of the Translator.
18
+
Gets the set of languages currently supported by other operations of the Translator.
19
19
20
20
## Request URL
21
21
@@ -37,9 +37,11 @@ Request parameters passed on the query string are:
37
37
</tr>
38
38
<tr>
39
39
<td>scope</td>
40
-
<td>*Optional parameter*.<br/>A comma-separated list of names defining the group of languages to return. Allowed group names are: `translation`, `transliteration` and `dictionary`. If no scope is given, then all groups are returned, which is equivalent to passing `scope=translation,transliteration,dictionary`. To decide which set of supported languages is appropriate for your scenario, see the description of the [response object](#response-body).</td>
40
+
<td>*Optional parameter*.<br/>A comma-separated list of names defining the group of languages to return. Allowed group names are: `translation`, `transliteration` and `dictionary`. If no scope is given, then all groups are returned, which is equivalent to passing `scope=translation,transliteration,dictionary`.</td>
41
41
</tr>
42
-
</table>
42
+
</table>
43
+
44
+
*See*[response body](#response-body).
43
45
44
46
Request headers are:
45
47
@@ -48,14 +50,14 @@ Request headers are:
48
50
<th>Description</th>
49
51
<tr>
50
52
<td>Accept-Language</td>
51
-
<td>*Optional request header*.<br/>The language to use for user interface strings. Some of the fields in the response are names of languages or names of regions. Use this parameter to define the language in which these names are returned. The language is specified by providing a well-formed BCP 47 language tag. For instance, use the value `fr` to request names in French or use the value `zh-Hant` to request names in Chinese Traditional.<br/>Names are provided in the English language when a target language is not specified or when localization is not available.
53
+
<td>*Optional request header*.<br/>The language to use for user interface strings. Some of the fields in the response are names of languages or names of regions. Use this parameter to define the language in which these names are returned. The language is specified by providing a well-formed BCP 47 language tag. For instance, use the value `fr` to request names in French or use the value `zh-Hant` to request names in Chinese Traditional.<br/>Names are provided in the English language when a target language isn't specified or when localization isn't available.
52
54
</td>
53
55
</tr>
54
56
<tr>
55
57
<td>X-ClientTraceId</td>
56
58
<td>*Optional request header*.<br/>A client-generated GUID to uniquely identify the request.</td>
57
59
</tr>
58
-
</table>
60
+
</table>
59
61
60
62
Authentication isn't required to get language resources.
61
63
@@ -100,7 +102,7 @@ The value for each property is as follows.
100
102
*`dir`: Directionality, which is `rtl` for right-to-left languages or `ltr` for left-to-right languages.
101
103
102
104
An example is:
103
-
105
+
104
106
```json
105
107
{
106
108
"translation": {
@@ -197,7 +199,7 @@ The value for each property is as follows.
197
199
*`nativeName`: Display name of the target language in the locale native for the target language.
198
200
199
201
*`dir`: Directionality, which is `rtl` for right-to-left languages or `ltr` for left-to-right languages.
200
-
202
+
201
203
*`code`: Language code identifying the target language.
202
204
203
205
An example is:
@@ -218,9 +220,9 @@ The value for each property is as follows.
218
220
},
219
221
```
220
222
221
-
The structure of the response object will not change without a change in the version of the API. For the same version of the API, the list of available languages may change over time because Microsoft Translator continually extends the list of languages supported by its services.
223
+
The structure of the response object doesn't change without a change in the version of the API. For the same version of the API, the list of available languages may change over time because Microsoft Translator continually extends the list of languages supported by its services.
222
224
223
-
The list of supported languages will not change frequently. To save network bandwidth and improve responsiveness, a client application should consider caching language resources and the corresponding entity tag (`ETag`). Then, the client application can periodically (for example, once every 24 hours) query the service to fetch the latest set of supported languages. Passing the current `ETag` value in an `If-None-Match` header field will allow the service to optimize the response. If the resource has not been modified, the service will return status code 304 and an empty response body.
225
+
The list of supported languages doesn't change frequently. To save network bandwidth and improve responsiveness, a client application should consider caching language resources and the corresponding entity tag (`ETag`). Then, the client application can periodically (for example, once every 24 hours) query the service to fetch the latest set of supported languages. Passing the current `ETag` value in an `If-None-Match` header field allows the service to optimize the response. If the resource hasn't been modified, the service returns status code 304 and an empty response body.
224
226
225
227
## Response headers
226
228
@@ -234,13 +236,13 @@ The list of supported languages will not change frequently. To save network band
234
236
</tr>
235
237
<tr>
236
238
<td>X-RequestId</td>
237
-
<td>Value generated by the service to identify the request. It is used for troubleshooting purposes.</td>
239
+
<td>Value generated by the service to identify the request. It's used for troubleshooting purposes.</td>
238
240
</tr>
239
-
</table>
241
+
</table>
240
242
241
243
## Response status codes
242
244
243
-
The following are the possible HTTP status codes that a request returns.
245
+
The following are the possible HTTP status codes that a request returns.
244
246
245
247
<tablewidth="100%">
246
248
<thwidth="20%">Status Code</th>
@@ -251,7 +253,7 @@ The following are the possible HTTP status codes that a request returns.
251
253
</tr>
252
254
<tr>
253
255
<td>304</td>
254
-
<td>The resource has not been modified since the version specified by request headers `If-None-Match`.</td>
256
+
<td>The resource hasn't been modified since the version specified by request headers `If-None-Match`.</td>
255
257
</tr>
256
258
<tr>
257
259
<td>400</td>
@@ -269,9 +271,9 @@ The following are the possible HTTP status codes that a request returns.
269
271
<td>503</td>
270
272
<td>Server temporarily unavailable. Retry the request. If the error persists, report it with: date and time of the failure, request identifier from response header `X-RequestId`, and client identifier from request header `X-ClientTraceId`.</td>
271
273
</tr>
272
-
</table>
274
+
</table>
273
275
274
-
If an error occurs, the request will also return a JSON error response. The error code is a 6-digit number combining the 3-digit HTTP status code followed by a 3-digit number to further categorize the error. Common error codes can be found on the [v3 Translator reference page](./v3-0-reference.md#errors).
276
+
If an error occurs, the request also returns a JSON error response. The error code is a 6-digit number combining the 3-digit HTTP status code followed by a 3-digit number to further categorize the error. Common error codes can be found on the [v3 Translator reference page](./v3-0-reference.md#errors).
Azure Private Link enables you to access Azure PaaS Services (for example, Azure Storage and SQL Database) and Azure hosted customer-owned/partner services over a [private endpoint](private-endpoint-overview.md) in your virtual network.
15
15
16
16
> [!IMPORTANT]
17
-
> Azure Private Link is now generally available. Both Private Endpoint and Private Link service (service behind standard load balancer) are generally available. Different Azure PaaS will onboard to Azure Private Link at different schedules. For known limitations, see [Private Endpoint](private-endpoint-overview.md#limitations) and [Private Link Service](private-link-service-overview.md#limitations).
17
+
> Azure Private Link is now generally available. Both Private Endpoint and Private Link service (service behind standard load balancer) are generally available. For known limitations, see [Private Endpoint](private-endpoint-overview.md#limitations) and [Private Link Service](private-link-service-overview.md#limitations).
description: Azure Service Manager Retirement documentation for all classic compute, networking and storage resources
4
+
author: surbhijain
5
+
ms.topic: overview
6
+
ms.date: 03/24/2023
7
+
ms.author: surbhijain
8
+
ms.service: reliability
9
+
10
+
---
11
+
12
+
# Azure Service Manager Retirement
13
+
14
+
Azure Service Manager (ASM) is the old control plane of Azure responsible for creating, managing, deleting VMs and performing other control plane operations, and has been in use since 2011. However, ASM is retiring in August 2024, and customers can now migrate to [Azure Resource Manager (ARM)](/azure/azure-resource-manager/management/overview). ARM provides a management layer that enables you to create, update, and delete resources in your Azure account. You can use management features like access control, locks, and tags to secure and organize your resources after deployment
15
+
16
+
## Benefits of migrating to ARM
17
+
Migrating from the classic resource model to ARM offers several benefits, including:
18
+
19
+
- Manage your infrastructure through declarative templates rather than scripts.
20
+
21
+
- Deploy, manage, and monitor all the resources for your solution as a group, rather than handling these resources individually.
22
+
23
+
- Redeploy your solution throughout the development lifecycle and have confidence your resources are deployed in a consistent state.
24
+
25
+
- Define the dependencies between resources so they're deployed in the correct order.
26
+
27
+
- Apply access control to all services because Azure role-based access control (Azure RBAC) is natively integrated into the management platform.
28
+
29
+
- Apply tags to resources to logically organize all the resources in your subscription.
30
+
31
+
- Clarify your organization's billing by viewing costs for a group of resources sharing the same tag.
32
+
33
+
There are many service-related benefits which can be found in the migration guides.
34
+
35
+
## Services being retired
36
+
To help with this transition, we are providing a range of resources and tools, including documentation and migration guides. We encourage you to begin planning your migration to ARM as soon as possible to ensure that you can continue to take advantage of the latest Azure features and capabilities.
37
+
Here is a list of classic resources being retired and their retirement dates:
|[Azure Batch Cloud Service Pools](https://azure.microsoft.com/updates/azure-batch-cloudserviceconfiguration-pools-will-be-retired-on-29-february-2024)| Feb 24 |
43
+
|[Cloud Services (classic)](https://azure.microsoft.com/updates/cloud-services-retirement-announcement)| Aug 24 |
44
+
|[App Services](https://azure.microsoft.com/updates/app-service-environment-v1-and-v2-retirement-announcement)| Aug 24 |
45
+
|[Classic Resource Providers](https://azure.microsoft.com/updates/azure-classic-resource-providers-will-be-retired-on-31-august-2024/)| Aug 24 |
46
+
|[Integration Services Environment](https://azure.microsoft.com/updates/integration-services-environment-will-be-retired-on-31-august-2024-transition-to-logic-apps-standard/)| Aug 24 |
47
+
|[Classic Storage](https://azure.microsoft.com/updates/classic-azure-storage-accounts-will-be-retired-on-31-august-2024/)| Aug 24 |
48
+
|[Classic Virtual Network](https://azure.microsoft.com/updates/five-azure-classic-networking-services-will-be-retired-on-31-august-2024/)| Aug 24 |
49
+
|[Classic Application Gateway](https://azure.microsoft.com/updates/five-azure-classic-networking-services-will-be-retired-on-31-august-2024/)| Aug 24 |
50
+
|[Classic Reserved IP addresses](https://azure.microsoft.com/updates/five-azure-classic-networking-services-will-be-retired-on-31-august-2024/)|Aug 24|
|[Azure Active Directory Domain Services](/azure/active-directory-domain-services/migrate-from-classic-vnet)| Mar 23 |
58
+
59
+
## Support
60
+
We understand that you may have questions or concerns about this change, and we are here to help. If you have any questions or require further information, please do not hesitate to reach out to our [customer support team](https://azure.microsoft.com/support)
0 commit comments