Merge pull request #99103 from Juliako/patch-156

Update assets-concept.md

Author: PRMerger15

articles/media-services/latest/assets-concept.md

@@ -26,7 +26,13 @@ An Asset is mapped to a blob container in the [Azure Storage account](storage-ac
 
 The **Archive** storage tier is only recommended for very large source files that have already been encoded and the encoding Job output was put in an output blob container. The blobs in the output container that you want to associate with an Asset and use to stream or analyze your content must exist in a **Hot** or **Cool** storage tier.
 
-### Naming blobs
+### Naming 
+
+#### Assets
+
+Asset's names must be unique. Media Services v3 resource names (for example, Assets, Jobs, Transforms) are subject to Azure Resource Manager naming constraints. For more information, see [Naming conventions](media-services-apis-overview.md#naming-conventions).
+
+#### Blobs
 
 The names of files/blobs within an asset must follow both the [blob name requirements](https://docs.microsoft.com/rest/api/storageservices/Naming-and-Referencing-Containers--Blobs--and-Metadata) and the [NTFS name requirements](https://docs.microsoft.com/windows/win32/fileio/naming-a-file). The reason for these requirements is the files can get copied from blob storage to a local NTFS disk for processing.
 

articles/media-services/latest/migrate-from-v2-to-v3.md

@@ -75,7 +75,7 @@ If you have a video service developed today on top of the [legacy Media Services
 * In v2, XML [input](../previous/media-services-input-metadata-schema.md) and [output](../previous/media-services-output-metadata-schema.md) metadata files get generated as the result of an encoding job. In v3, the metadata format changed from XML to JSON. 
 
 > [!NOTE]
-> Review the naming conventions that are applied to [Media Services v3 resources](media-services-apis-overview.md#naming-conventions). Also review [naming blobs](assets-concept.md#naming-blobs).
+> Review the naming conventions that are applied to [Media Services v3 resources](media-services-apis-overview.md#naming-conventions). Also review [naming blobs](assets-concept.md#naming).
 
 ## Feature gaps with respect to v2 APIs