Merge pull request #107602 from vhorne/fwm-over

update known issues

Author: PRMerger18

articles/firewall-manager/overview.md

@@ -5,7 +5,7 @@ author: vhorne
 ms.service: firewall-manager
 services: firewall-manager
 ms.topic: overview
-ms.date: 02/18/2020
+ms.date: 03/13/2020
 ms.author: victorh
 ---
 
@@ -75,13 +75,14 @@ Azure Firewall Manager Preview has the following known issues:
 
 |Issue  |Description  |Mitigation  |
 |---------|---------|---------|
-|Third-party filtering limitations|V2I traffic filtering with third-party providers is not supported with Azure Firewall B2V and V2V.|Currently investigating.|
-|Traffic splitting not currently supported|Office 365 and Azure Public PaaS traffic splitting is not currently supported. As such, selecting a third-party provider for V2I or B2I also sends all Azure Public PaaS and Office 365 traffic via the partner service.|Currently investigating traffic splitting at the hub.
-|One secured virtual hub per region|You can't have more than one secured virtual hub per region|Create multiple virtual WANs in a region.|
-|Base policies must be in same region as local policy|Create all your local policies in the same region as the base policy. You can still apply a policy that was created in one region on a secured hub from another region.|Currently investigating.|
-|Inter-hub communication not working with Secured Virtual Hub|Secured Virtual Hub to Secured Virtual Hub communication is not yet supported.|Currently investigating.|
+|Third-party filtering limitations.|V2I traffic filtering with third-party providers is not supported with Azure Firewall B2V and V2V.|Investigating|
+|Traffic splitting not currently supported.|Office 365 and Azure Public PaaS traffic splitting is not currently supported. As such, selecting a third-party provider for V2I or B2I also sends all Azure Public PaaS and Office 365 traffic via the partner service.|Investigating traffic splitting at the hub.
+|One secured virtual hub per region.|You can't have more than one secured virtual hub per region.|Create multiple virtual WANs in a region.|
+|Base policies must be in same region as local policy.|Create all your local policies in the same region as the base policy. You can still apply a policy that was created in one region on a secured hub from another region.|Investigating|
+|Inter-hub communication not working with Secured Virtual Hub|Secured Virtual Hub to Secured Virtual Hub communication is not yet supported.|Investigating|
 |All Secured Virtual Hubs sharing the same virtual WAN must be in the same resource group.|This behavior is aligned with Virtual WAN Hubs today.|Create multiple Virtual WANs to allow Secured Virtual Hubs to be created in different resource groups.|
-|IP Groups are not supported in Firewall Policy|IP Groups are in public preview and currently only supported with traditional firewall rules|Fix in progress
+|IP Groups are not supported in Firewall Policy.|IP Groups are in public preview and currently only supported with traditional firewall rules.|Fix in progress.
+|Cloud Solution Provider (CSP) subscriptions not supported.|Currently, [CSP subscriptions](https://azure.microsoft.com/offers/ms-azr-0145p/) are not supported.|Investigating
 
 ## Next steps