split an article

Author: Juliako

articles/media-services/latest/TOC.yml

@@ -201,7 +201,7 @@ t- name: Media Services Documentation
       href: media-services-high-availability-streaming.md
   - name: Migration from v2 to v3
     items:
-    - name: v2 vs. v3
+    - name: v2 vs v3
       href: media-services-v2-vs-v3.md
     - name: Migration guidance
       href: migrate-from-v2-to-v3.md 

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

@@ -38,36 +38,9 @@ Asset's names must be unique. Media Services v3 resource names (for example, Ass
 
 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.
 
-## Map v3 asset properties to v2
+## Asset changes between Media Services v2 and v3
 
-The following table shows how the [Asset](https://docs.microsoft.com/rest/api/media/assets/createorupdate#asset)'s properties in v3 map to Asset's properties in v2.
-
-|v3 properties|v2 properties|
-|---|---|
-|`id` - (unique) the full Azure Resource Manager path, see examples in [Asset](https://docs.microsoft.com/rest/api/media/assets/createorupdate)||
-|`name` - (unique) see [Naming conventions](media-services-apis-overview.md#naming-conventions) ||
-|`alternateId`|`AlternateId`|
-|`assetId`|`Id` - (unique) value starts with the `nb:cid:UUID:` prefix.|
-|`created`|`Created`|
-|`description`|`Name`|
-|`lastModified`|`LastModified`|
-|`storageAccountName`|`StorageAccountName`|
-|`storageEncryptionFormat`| `Options` (creation options)|
-|`type`||
-
-## Storage side encryption
-
-To protect your Assets at rest, the assets should be encrypted by the storage side encryption. The following table shows how the storage side encryption works in Media Services:
-
-|Encryption option|Description|Media Services v2|Media Services v3|
-|---|---|---|---|
-|Media Services Storage Encryption|AES-256 encryption, key managed by Media Services.|Supported<sup>(1)</sup>|Not supported<sup>(2)</sup>|
-|[Storage Service Encryption for Data at Rest](https://docs.microsoft.com/azure/storage/common/storage-service-encryption)|Server-side encryption offered by Azure Storage, key managed by Azure or by customer.|Supported|Supported|
-|[Storage Client-Side Encryption](https://docs.microsoft.com/azure/storage/common/storage-client-side-encryption)|Client-side encryption offered by Azure storage, key managed by customer in Key Vault.|Not supported|Not supported|
-
-<sup>1</sup> While Media Services does support handling of content in the clear/without any form of encryption, doing so isn't recommended.
-
-<sup>2</sup> In Media Services v3, storage encryption (AES-256 encryption) is only supported for backwards compatibility when your Assets were created with Media Services v2. Meaning v3 works with existing storage encrypted assets but won't allow creation of new ones.
+See [Asset changes between Media Services v2 and v3](media-services-v2-vs-v3.md#asset-specific-changes)
 
 ## Next steps