Azure Media Services v3 release notes

To stay up-to-date with the most recent developments, this article provides you with information about:

• The latest releases
• Known issues
• Bug fixes
• Deprecated functionality

September 2021

New basic pass-through live event SKU

The new basic pass-through live event SKU allows customers to create live events at a lower price point. It is similar to standard pass-through live events, but with lower input bandwidth limits, fewer live output allowed, different DVR window length limits, and no access to live transcription. See live event types comparison for more details.

Improved scale management and monitoring for a Streaming Endpoint in the portal

The streaming endpoint portal page now provides an easy way for you to manage your egress capacity and estimate your audience reach with and without a CDN configured. Simply adjust the delivery bitrate and expected CDN cache hit ratio to get quick estimations of your audience size and help you determine if you need to scale up to more Premium streaming endpoints.

Streaming Endpoint portal page now shows CPU, egress and latency metrics

You can now visualize the CPU load, egress bandwidth and end-to-end latency metrics on their streaming endpoints in the Azure portal. You can now create monitoring alerts based on the CPU, egress or latency metrics directly in the portal using the power of Azure Monitor.

User-Assigned Managed Identities support for Media Services accounts

Using User-Assigned Managed Identities, customers will now be able to enable better security of their storage accounts and associated key vaults. Access to the customer storage account and key vaults will be limited to the user assigned managed identity. You have full control over the lifetime of user-managed identities and can easily revoke the media service account’s access to any specific storage account as needed.

Media services storage accounts page in the portal now support both UAMI and SAMI

You can now assign and manage user-assigned managed identities (UAMI) or system-assigned managed identities(SAMI) for your storage accounts directly in the Azure portal for Media Services.

Bring your own key page now also supports both UAMI and SAMI.

The key management portal page for Media Services now supports configuration and management of user-assigned managed identities (UAMI) or system-assigned managed identities (SAMI).

Private Link support for Media services

You can now restrict public access to your live events, streaming endpoints, and key delivery services endpoint for content protection and DRM by creating a private endpoint for each of the services. This will limit public access to each of these services. Only traffic originating from your configured virtual network (VNET), configured in Private Endpoint, will be able reach these endpoints.

IP Allow list for Key Service

You can now choose to allow certain public IP addresses to have access to the key delivery service for DRM and content protection. Live event and streaming endpoints already support configuration of IP Allow List in their respective pages.

You also now have an account level feature flag to allow/block public internet access to your media services account.

July 2021

.NET SDK (Microsoft.Azure.Management.Media ) 5.0.0 release available in NuGet

The Microsoft.Azure.Management.Media .NET SDK version 5.0.0 is now released on NuGet. This version is generated to work with the 2021-06-01 stable version of the Open API (Swagger) ARM Rest API.

For details on changes from the 4.0.0 release see the change log.

Changes in the 5.0.0 .NET SDK release

• The Media Services account now supports system and user assigned managed identities.
• Added PublicNetworkAccess option to Media Services accounts. This option can be used with the Private Link feature to only allow access from private networks, blocking all public network access
• Basic passthrough - A new live event type is added. "Basic Pass-through" live events have similar capabilities as standard pass-through live events with some input and output restrictions, and are offered at a reduced price.
• PresetConfigurations - allow you to customize the output settings, and min and max bitrates used for the Content Aware Encoding presets. This helps you to better estimate and plan for more accurate billing when using Content Aware Encoding through constrained output track numbers and resolutions.

Breaking changes in tht 5.0.0 .NET SDK release

• ApiErrorException has been replaced with ErrorResponseException to be consistent with all other Azure SDKs. Exception body has not changed.
• All calls returning 404 Not found now raise an ErrorResponseException instead of returning null. this change was made to be consistent with other Azure SDKs
• Media service constructor has new optional PublicNetworkAccess parameter after KeyDelivery parameter.
• Type property in MediaServiceIdentity has been changed from ManagedIdentityType enum to string to accommodate multiple comma-separated values. Valid strings are SystemAssigned or UserAssigned.

June 2021

Additional Live Event ingest heartbeat properties for improved diagnostics

Additional live event ingest heartbeat properties have been added to the Event Grid message. This includes the following new fields to assist with diagnosing issues during live ingest. The ingestDriftValue is helpful in scenarios where you need to monitor network latency from the source ingest encoder pushing into the live event. If this value drifts out too far, it can be an indication that the network latency is too high for a successful live streaming event.

See the LiveEventIngestHeartbeat schema for more details.

Private links support is now GA

Support for using Media Services with private links is now GA and available in all Azure regions including Azure Government clouds. Azure Private Link enables you to access Azure PaaS Services and Azure hosted customer-owned/partner services over a Private Endpoint in your virtual network. Traffic between your virtual network and the service traverses over the Microsoft backbone network, eliminating exposure from the public Internet.

For details on how to use Media Services with private links, see Create a Media Services and Storage account with a Private Link

New US West 3 region is GA

The US West 3 region is now GA and available for customers to use when creating new Media Services accounts.

Key delivery supports IP allow list restrictions

Media Services accounts can now be configured with IP allow list restrictions on key delivery. The new allow list setting is available on the Media Services account resource through the SDK as well as in the portal and CLI. This allows operators to restrict delivery of DRM licenses and AES-128 content keys to specific IPv4 ranges.

This feature can also be used to shut off all public internet delivery of DRM licenses or AES-128 keys and restrict delivery to a private network endpoint.

See the article Restrict access to DRM license and AES key delivery using IP allowlists for details.

New Samples for Python and Node.js (with Typescript)

Updated samples for Node.js that use the latest Typescript support in the Azure SDK.

New Python sample demonstrating how to use Azure Functions, and Event Grid to trigger Face redaction preset.

May 2021

Availability Zones default support in Media Services

Media Services now supports Availability Zones, providing fault-isolated locations within the same Azure region. Media Services accounts are zone redundant by default now and there is no additional configuration or settings required. This only applies to regions that have Availability Zones support

March 2021

New language support added to the AudioAnalyzer preset

Additional languages for video transcription and subtitling are available now in the AudioAnalyzer preset (both Basic and Standard modes).

• English (Australia), 'en-AU'
• French (Canada), 'fr-CA'
• Arabic (Bahrain) modern standard, 'ar-BH'
• Arabic (Egypt), 'ar-EG'
• Arabic (Iraq), 'ar-IQ'
• Arabic (Israel), 'ar-IL'
• Arabic (Jordan), 'ar-JO'
• Arabic (Kuwait), 'ar-KW'
• Arabic (Lebanon), 'ar-LB'
• Arabic (Oman), 'ar-OM'
• Arabic (Qatar), 'ar-QA'
• Arabic (Saudi Arabia), 'ar-SA'
• Danish, ‘da-DK’
• Norwegian, 'nb-NO'
• Swedish, ‘sv-SE’
• Finnish, ‘fi-FI’
• Thai, ‘th-TH’
• Turkish, ‘tr-TR’

See the latest available languages in the Analyzing Video And Audio Files concept article.

February 2021

HEVC Encoding support in Standard Encoder

The Standard Encoder now supports 8-bit HEVC (H.265) encoding support. HEVC content can be delivered and packaged through the Dynamic Packager using the 'hev1' format.

A new .NET custom encoding with HEVC sample is available in the media-services-v3-dotnet Git Hub repository. In addition to custom encoding, the following new built-in HEVC encoding presets are now available:

• H265ContentAwareEncoding
• H265AdaptiveStreaming
• H265SingleBitrate720P
• H265SingleBitrate1080p
• H265SingleBitrate4K

Customers previously using HEVC in the Premium Encoder in the v2 API should migrate to use the new HEVC encoding support in the Standard Encoder.

Azure Media Services v2 API and SDKs deprecation announcement

Update your Azure Media Services REST API and SDKs to v3 by 29 February 2024

Because version 3 of Azure Media Services REST API and client SDKs for .NET and Java offers more capabilities than version 2, we’re retiring version 2 of the Azure Media Services REST API and client SDKs for .NET and Java.

We encourage you to make the switch sooner to gain the richer benefits of version 3 of Azure Media Services REST API and client SDKs for .NET and Java. Version 3 provides:

• 24x7 live event support
• ARM REST APIs, client SDKs for .NET core, Node.js, Python, Java, Go and Ruby.
• Customer managed keys, trusted storage integration, private link support, and more

As part of the update to v3 API and SDKs, Media Reserve Units (MRUs) are no longer needed for any Media Services account as the system will automatically scale up and down based on load. Please refer to the MRUs migration guidance for more information.

Action Required

To minimize disruption to your workloads, review the migration guide to transition your code from the version 2 API and SDKs to version 3 API and SDK before 29 February 2024. After 29 February 2024, Azure Media Services will no longer accept traffic on the version 2 REST API, the ARM account management API version 2015-10-01, or from the version 2 .NET client SDKs. This includes any 3rd party open-source client SDKS that may call the version 2 API.

See the official Azure Updates announcement.

Standard Encoder support for v2 API features

In addition to the new added support for HEVC (H.265) encoding, the following features are now available in the 2020-05-01 (or later) version of the encoding API.

• Multiple Input File stitching is now supported using the new JobInputClip support.
  • An example is available for .NET showing how to stitch two assets together.
• Audio track selection allows customers to select and map the incoming audio tracks and route them to the output for encoding
  • See the REST API OpenAPI for details on AudioTrackDescriptor and track selection
• Track selection for encoding – allows customers to choose tracks from an ABR source file or live archive that has multiple bitrate tracks. Extremely helpful for generating MP4s from the live event archive files.
  • See VideoTrackDescriptor
• Redaction (blurring) capabilities added to FaceDetector
  • See the Redact and Combined modes of the FaceDetector Preset

New client SDK releases for 2020-05-01 version of the Azure Media Services API

New client SDK versions for all available languages are now available with the above features. Please update to the latest client SDKs in your code bases using your package manager.

• .NET SDK package 3.0.4
• Node.js Typescript version 8.1.0
• Python azure-mgmt-media 3.1.0
• Java SDK 1.0.0-beta.2

New Security features available in the 2020-05-01 version of the Azure Media Services API

• Customer Managed Keys: Content Keys and other data stored in accounts created with the "2020-05-01" version API are encrypted with an account key. Customers can provide a key to encrypt the account key.

• Trusted Storage: Media Services can be configured to access Azure Storage using a Managed Identity associated with the Media Services account. When storage accounts are accessed using a Managed Identity, customers can configure more restrictive network ACLs on the storage account without blocking Media Services scenarios.

• Managed Identities: Customers may enable a System Assigned Managed Identity for a Media Services account to provide access to Key Vaults (for Customer Managed Keys) and storage accounts (for Trusted Storage).

Updated Typescript Node.js Samples using isomorphic SDK for JavaScript

The Node.js samples have been updated to use the latest isomorphic SDK. The samples now show use of Typescript. In addition, a new live streaming sample was added for Node.js/Typescript.

See the latest samples in the media-services-v3-node-tutorials Git Hub repo.

New Live Stand-by mode to support faster startup from warm state

Live Events now support a lower-cost billing mode for "stand-by". This allows customers to pre-allocate Live Events at a lower cost for the creation of "hot pools". Customers can then use the stand-by live events to transition to the Running state faster than starting from cold on creation. This reduces the time to start the channel significantly and allows for fast hot-pool allocation of machines running in a lower price mode. See the latest pricing details here. For more information on the StandBy state and the other states of Live Events see the article - Live event states and billing.

December 2020

Regional availability

Azure Media Services is now available in the Norway East region in the Azure portal. There is no restV2 in this region.

October 2020

Basic Audio Analysis

The Audio Analysis preset now includes a Basic mode pricing tier. The new Basic Audio Analyzer mode provides a low-cost option to extract speech transcription, and format output captions and subtitles. This mode performs speech-to-text transcription and generation of a VTT subtitle/caption file. The output of this mode includes an Insights JSON file including only the keywords, transcription,and timing information. Automatic language detection and speaker diarization are not included in this mode. See the list of supported languages.

Customers using Indexer v1 and Indexer v2 should migrate to the Basic Audio Analysis preset.

For more information about the Basic Audio Analyzer mode, see Analyzing Video and Audio files. To learn to use the Basic Audio Analyzer mode with the REST API, see How to Create a Basic Audio Transform.

Live Events

Updates to most properties are now allowed when live events are stopped. In addition, users are allowed to specify a prefix for the static hostname for the live event's input and preview URLs. VanityUrl is now called useStaticHostName to better reflect the intent of the property.

Live events now have a StandBy state. See Live Events and Live Outputs in Media Services.

A live event supports receiving various input aspect ratios. Stretch mode allows customers to specify the stretching behavior for the output.

Live encoding now adds the capability of outputting fixed key frame interval fragments between 0.5 to 20 seconds.

Accounts

August 2020

Dynamic Encryption

Support for the legacy PlayReady Protected Interoperable File Format (PIFF 1.1) encryption is now available in the Dynamic Packager. This provides support for legacy Smart TV sets from Samsung and LG that implemented the early drafts of the Common Encryption standard (CENC) published by Microsoft. The PIFF 1.1 format is also known as the encryption format that was previously supported by the Silverlight client library. Today, the only use case scenario for this encryption format is to target the legacy Smart TV market where there remains a non-trivial number of Smart TVs in some regions that only support Smooth Streaming with PIFF 1.1 encryption.

To use the new PIFF 1.1 encryption support, change the encryption value to 'piff' in the URL path of the Streaming Locator. For more details, see the Content Protection overview. For Example: https://amsv3account-usw22.streaming.media.azure.net/00000000-0000-0000-0000-000000000000/ignite.ism/manifest(encryption=piff)|

July 2020

Live transcriptions

Live Transcriptions now supports 19 languages and 8 regions.

Protecting your content with Media Services and Azure AD

We published a tutorial called End-to-End content protection using Azure AD.

High availability

We published a High Availability with Media Services and Video on Demand (VOD) overview and sample.

June 2020

Live Video Analytics on IoT Edge preview release

The preview of Live Video Analytics on IoT Edge went public.

Live Video Analytics on IoT Edge is an expansion to the Media Service family. It enables you to analyze live video with AI models of your choice on your own edge devices, and optionally capture and record that video. You can now build apps with real-time video analytics at the edge without worrying about the complexity of building and operating a live video pipeline.

May 2020

Azure Media Services is now generally available in the following regions: "Germany North", "Germany West Central", "Switzerland North", and "Switzerland West". Customers can deploy Media Services to these regions using the Azure portal.

April 2020

Improvements in documentation

Azure Media Player docs were migrated to the Azure documentation.

January 2020

Improvements in media processors

• Improved support for interlaced sources in Video Analysis – such content is now de-interlaced correctly before being sent to inference engines.
• When generating thumbnails with the “Best” mode, the encoder now searches beyond 30 seconds to select a frame that is not monochromatic.

Azure Government cloud updates

Media Services GA’ed in the following Azure Government regions: USGov Arizona and USGov Texas.

December 2019

Added CDN support for Origin-Assist Prefetch headers for both live and video on-demand streaming; available for customers who have direct contract with Akamai CDN. Origin-Assist CDN-Prefetch feature involves the following HTTP header exchanges between Akamai CDN and Azure Media Services origin:

To see part of the header exchange in action, you can try the following steps:

1. Use Postman or curl to issue a request to Media Services origin for an audio or video segment or fragment. Make sure to add the header CDN-Origin-Assist-Prefetch-Enabled: 1 in the request.
2. In the response, you should see the header CDN-Origin-Assist-Prefetch-Path with a relative path as its value.

November 2019

Live transcription Preview

Live transcription is now in public preview and available for use in the West US 2 region.

Live transcription is designed to work in conjunction with live events as an add-on capability. It is supported on both pass-through and Standard or Premium encoding live events. When this feature is enabled, the service uses the Speech-To-Text feature of Cognitive Services to transcribe the spoken words in the incoming audio into text. This text is then made available for delivery along with video and audio in MPEG-DASH and HLS protocols. Billing is based on a new add-on meter that is additional cost to the live event when it is in the "Running" state. For details on Live transcription and billing, see Live transcription

Content protection

The Token Replay Prevention feature released in limited regions back in September is now available in all regions. Media Services customers can now set a limit on the number of times the same token can be used to request a key or a license. For more information, see Token Replay Prevention.

New recommended live encoder partners

Added support for the following new recommended partner encoders for RTMP live streaming:

• Cambria Live 4.3
• GoPro Hero7/8 and Max action cameras
• Restream.io

File Encoding enhancements

• A new Content Aware Encoding preset is now available. It produces a set of GOP-aligned MP4s by using content-aware encoding. Given any input content, the service performs an initial lightweight analysis of the input content. It uses those results to determine the optimal number of layers, appropriate bit rate, and resolution settings for delivery by adaptive streaming. This preset is particularly effective for low-complexity and medium-complexity videos, where the output files are at lower bit rates but at a quality that still delivers a good experience to viewers. The output will contain MP4 files with video and audio interleaved. For more information, see the open API specs.
• Improved performance and multi-threading for the resizer in Standard Encoder. Under specific conditions, customer should see a performance boost between 5-40% VOD encoding. Low complexity content encoded into multiple bit-rates will see the highest performance increases.
• Standard encoding now maintains a regular GOP cadence for variable frame rate (VFR) contents during VOD encoding when using the time-based GOP setting. This means that customer submitting mixed frame rate content that varies between 15-30 fps, for example, should now see regular GOP distances calculated on output to adaptive bitrate streaming MP4 files. This will improve the ability to switch seamlessly between tracks when delivering over HLS or DASH.
• Improved AV sync for variable frame rate (VFR) source content

Azure Video Analyzer for Media, Video analytics

• Keyframes extracted using the VideoAnalyzer preset are now in the original resolution of the video instead of being resized. High-resolution keyframe extraction gives you original quality images and allows you to make use of the image-based artificial intelligence models provided by the Microsoft Computer Vision and Custom Vision services to gain even more insights from your video.

September 2019

Media Services v3

Live linear encoding of live events

Media Services v3 is announcing the preview of 24 hrs x 365 days of live linear encoding of live events.

Media Services v2

Deprecation of media processors

We are announcing deprecation of Azure Media Indexer and Azure Media Indexer 2 Preview. For the retirement dates, see the legacy components article. Azure Video Analyzer for Media replaces these legacy media processors.

For more information, see Migrate from Azure Media Indexer and Azure Media Indexer 2 to Azure Media Services Video Indexer.

August 2019

Media Services v3

South Africa regional pair is open for Media Services

Media Services is now available in South Africa North and South Africa West regions.

For more information, see Clouds and regions in which Media Services v3 exists.

Media Services v2

Deprecation of media processors

We are announcing deprecation of the Windows Azure Media Encoder (WAME) and Azure Media Encoder (AME) media processors, which are being retired. For the retirement dates, see this legacy components article.

For details, see Migrate WAME to Media Encoder Standard and Migrate AME to Media Encoder Standard.

July 2019

Content protection

When streaming content protected with token restriction, end users need to obtain a token that is sent as part of the key delivery request. The Token Replay Prevention feature allows Media Services customers to set a limit on how many times the same token can be used to request a key or a license. For more information, see Token Replay Prevention.

As of July, the preview feature was only available in US Central and US West Central.

June 2019

Video subclipping

You can now trim or subclip a video when encoding it using a Job.

This functionality works with any Transform that is built using either the BuiltInStandardEncoderPreset presets, or the StandardEncoderPreset presets.

See examples:

• Subclip a video with .NET
• Subclip a video with REST

May 2019

Azure Monitor support for Media Services diagnostic logs and metrics

You can now use Azure Monitor to view telemetry data emitted by Media Services.

• Use the Azure Monitor diagnostic logs to monitor requests sent by the Media Services Key Delivery endpoint.
• Monitor metrics emitted by Media Services Streaming Endpoints.

For details, see Monitor Media Services metrics and diagnostic logs.

Multi audio tracks support in Dynamic Packaging

When streaming Assets that have multiple audio tracks with multiple codecs and languages, Dynamic Packaging now supports multi audio tracks for the HLS output (version 4 or above).

Korea regional pair is open for Media Services

Media Services is now available in Korea Central and Korea South regions.

For more information, see Clouds and regions in which Media Services v3 exists.

Performance improvements

Added updates that include Media Services performance improvements.

• The maximum file size supported for processing was updated. See, Quotas, and limits.
• Encoding speeds improvements.

April 2019

New presets

• FaceDetectorPreset was added to the built-in analyzer presets.
• ContentAwareEncodingExperimental was added to the built-in encoder presets. For more information, see Content-aware encoding.

March 2019

Dynamic Packaging now supports Dolby Atmos. For more information, see Audio codecs supported by dynamic packaging.

You can now specify a list of asset or account filters, which would apply to your Streaming Locator. For more information, see Associate filters with Streaming Locator.

February 2019

Media Services v3 is now supported in Azure national clouds. Not all features are available in all clouds yet. For details, see Clouds and regions in which Azure Media Services v3 exists.

Microsoft.Media.JobOutputProgress event was added to the Azure Event Grid schemas for Media Services.

January 2019

Media Encoder Standard and MPI files

When encoding with Media Encoder Standard to produce MP4 file(s), a new .mpi file is generated and added to the output Asset. This MPI file is intended to improve performance for dynamic packaging and streaming scenarios.

You should not modify or remove the MPI file, or take any dependency in your service on the existence (or not) of such a file.

December 2018

Updates from the GA release of the V3 API include:

• The PresentationTimeRange properties are no longer 'required' for Asset Filters and Account Filters.
• The $top and $skip query options for Jobs and Transforms have been removed and $orderby was added. As part of adding the new ordering functionality, it was discovered that the $top and $skip options had accidentally been exposed previously even though they are not implemented.
• Enumeration extensibility was re-enabled. This feature was enabled in the preview versions of the SDK and got accidentally disabled in the GA version.
• Two predefined streaming policies have been renamed. SecureStreaming is now MultiDrmCencStreaming. SecureStreamingWithFairPlay is now Predefined_MultiDrmStreaming.

November 2018

The CLI 2.0 module is now available for Azure Media Services v3 GA – v 2.0.50.

New commands

• az ams account
• az ams account-filter
• az ams asset
• az ams asset-filter
• az ams content-key-policy
• az ams job
• az ams live-event
• az ams live-output
• az ams streaming-endpoint
• az ams streaming-locator
• az ams account mru - enables you to manage Media Reserved Units. For more information, see Scale Media Reserved Units.

New features and breaking changes

Asset commands

• --storage-account and --container arguments added.
• Default values for expiry time (Now+23h) and permissions (Read) in az ams asset get-sas-url command added.

Job commands

• --correlation-data and --label arguments added
• --output-asset-names renamed to --output-assets. Now it accepts a space-separated list of assets in 'assetName=label' format. An asset without label can be sent like this: 'assetName='.

Streaming Locator commands

• az ams streaming locator base command replaced with az ams streaming-locator.
• --streaming-locator-id and --alternative-media-id support arguments added.
• --content-keys argument argument updated.
• --content-policy-name renamed to --content-key-policy-name.

Streaming Policy commands

• az ams streaming policy base command replaced with az ams streaming-policy.
• Encryption parameters support in az ams streaming-policy create added.

Transform commands

• --preset-names argument replaced with --preset. Now you can only set 1 output/preset at a time (to add more you have to run az ams transform output add). Also, you can set custom StandardEncoderPreset by passing the path to your custom JSON.
• az ams transform output remove can be performed by passing the output index to remove.
• --relative-priority, --on-error, --audio-language and --insights-to-extract arguments added in az ams transform create and az ams transform output add commands.

October 2018 - GA

This section describes Azure Media Services (AMS) October updates.

REST v3 GA release

The REST v3 GA release includes more APIs for Live, Account/Asset level manifest filters, and DRM support.

Azure Resource Management

Support for Azure Resource Management enables unified management and operations API (now everything in one place).

Starting with this release, you can use Resource Manager templates to create Live Events.

Improvement of Asset operations

The following improvements were introduced:

• Ingest from HTTP(s) URLs or Azure Blob Storage SAS URLs.
• Specify you own container names for Assets.
• Easier output support to create custom workflows with Azure Functions.

New Transform object

The new Transform object simplifies the Encoding model. The new object makes it easy to create and share encoding Resource Manager templates and presets.

Azure Active Directory authentication and Azure RBAC

Azure AD Authentication and Azure role-based access control (Azure RBAC) enable secure Transforms, LiveEvents, Content Key Policies, or Assets by Role or Users in Azure AD.

Client SDKs

Languages supported in Media Services v3: .NET Core, Java, Node.js, Ruby, Typescript, Python, Go.

Live encoding updates

The following live encoding updates are introduced:

• New low latency mode for live (10 seconds end-to-end).

• Improved RTMP support (increased stability and more source encoder support).

• RTMPS secure ingest.

  When you create a Live Event, you now get 4 ingest URLs. The 4 ingest URLs are almost identical, have the same streaming token (AppId), only the port number part is different. Two of the URLs are primary and backup for RTMPS.

• 24-hour transcoding support.

• Improved ad-signaling support in RTMP via SCTE35.

Improved Event Grid support

You can see the following Event Grid support improvements:

• Azure Event Grid integration for easier development with Logic Apps and Azure Functions.
• Subscribe for events on Encoding, Live Channels, and more.

CMAF support

CMAF and 'cbcs' encryption support for Apple HLS (iOS 11+) and MPEG-DASH players that support CMAF.

Video Indexer

Video Indexer GA release was announced in August. For new information about currently supported features, see What is Video Indexer.

Plans for changes

Azure CLI 2.0

The Azure CLI 2.0 module that includes operations on all features (including Live, Content Key Policies, Account/Asset Filters, Streaming Policies) is coming soon.

Known issues

Only customers that used the preview API for Asset or AccountFilters are impacted by the following issue.

If you created Assets or Account Filters between 09/28 and 10/12 with Media Services v3 CLI or APIs, you need to remove all Asset and AccountFilters and re-create them due to a version conflict.

May 2018 - Preview

.NET SDK

The following features are present in the .NET SDK:

• Transforms and Jobs to encode or analyze media content. For examples, see Stream files and Analyze.
• Streaming Locators for publishing and streaming content to end-user devices
• Streaming Policies and Content Key Policies to configure key delivery and content protection (DRM) when delivering content.
• Live Events and Live Outputs to configure the ingest and archiving of live streaming content.
• Assets to store and publish media content in Azure Storage.
• Streaming Endpoints to configure and scale dynamic packaging, encryption, and streaming for both live and on-demand media content.

Known issues

• When submitting a job, you can specify to ingest your source video using HTTPS URLs, SAS URLs, or paths to files located in Azure Blob storage. Currently, Media Services v3 does not support chunked transfer encoding over HTTPS URLs.

Ask questions, give feedback, get updates

Check out the Azure Media Services community article to see different ways you can ask questions, give feedback, and get updates about Media Services.

See also

Migration guidance for moving from Media Services v2 to v3.

Next steps

• Overview
• Media Services v2 release notes