Merge pull request #186946 from Namandeep-MSFT/naman-v3-feature-gaps

Customer Support 1913124.

Author: hmacgregor1

articles/media-services/latest/migrate-v-2-v-3-differences-feature-gaps.md

@@ -9,7 +9,7 @@ ms.service: media-services
 ms.topic: conceptual
 ms.tgt_pltfrm: multiple
 ms.workload: media
-ms.date: 03/25/2021
+ms.date: 01/31/2022
 ms.author: inhenkel
 ---
 
@@ -21,19 +21,19 @@ ms.author: inhenkel
 
 ![migration steps 2](./media/migration-guide/steps-2.svg)
 
-This part of the migration guidance gives you detailed information about the
-differences between the V2 and V3 APIs.
+This part of the migration guidance gives you detailed information about the differences between the V2 and V3 APIs.
 
 ## Feature gaps between V2 and V3 APIs
 
 The V3 API has the following feature gaps with the V2 API. A couple
-of the advanced features of the Media Encoder Standard in V2 APIs are currently
-not available in V3:
+of the advanced features of the Media Encoder Standard in V2 APIs are currently not available in V3:
 
-- Inserting a silent audio track when input has no audio, as this is no longer required with the Azure Media Player.
+- Inserting a silent audio track when input has no audio or inserting a monochrome video track when input has no video, as this is no longer required with the Azure Media Player.
 
 - Inserting a video track when input has no video.
 
+- The `InsertBlackIfNoVideoBottomLayerOnly` and `InsertBlackIfNoVideo` flags are no longer supported in v3.
+
 - Live Events with transcoding currently don't support Slate insertion mid-stream and ad marker insertion via API call.
 
 - Azure Media Premium Encoder will no longer be supported in V2. If you're using it for 8-bit HEVC encoding, use the new HEVC support in the Standard Encoder. 
@@ -44,7 +44,7 @@ not available in V3:
 
 - In Media Services V3, FairPlay IV cannot be specified. While it doesn't impact customers using Media Services for both packaging and license delivery, it can be an issue when using a third-party DRM system to deliver the FairPlay licenses (hybrid mode).
 
-- Client-side storage encryption for protection of assets at rest has been removed in the V3 API and replaced by storage service encryption for data at rest. The V3 APIs continue to work with existing storage encrypted assets but won't allow creation of new ones.
+- Client-side storage encryption for protection of assets at rest has been removed in the V3 API and replaced by storage service encryption for data at rest. The V3 APIs continue to work with existing storage-encrypted assets but won't allow creation of new ones.
 
 ## Terminology and entity changes