Skip to content

Commit dd95d9d

Browse files
authored
Update assets-concept.md
1 parent 1367f25 commit dd95d9d

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

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

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@ editor: ''
1212
ms.service: media-services
1313
ms.workload:
1414
ms.topic: article
15-
ms.date: 08/29/2019
15+
ms.date: 03/09/2020
1616
ms.author: juliako
1717
ms.custom: seodec18
1818

1919
---
2020

21-
# Assets in Azure Media Services
21+
# Assets in Azure Media Services v3
2222

2323
In Azure Media Services, an [Asset](https://docs.microsoft.com/rest/api/media/assets) is a core concept. It is where you input media (for example, through upload or live ingest), output media (from a job output), and publish media from (for streaming).
2424

@@ -38,10 +38,6 @@ Asset's names must be unique. Media Services v3 resource names (for example, Ass
3838

3939
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.
4040

41-
## Asset changes between Media Services v2 and v3
42-
43-
See [Asset changes between Media Services v2 and v3](media-services-v2-vs-v3.md#asset-specific-changes)
44-
4541
## Next steps
4642

4743
[Manage assets in Media Services](manage-asset-concept.md)

0 commit comments

Comments
 (0)