Link fixes

Author: Mattp123

powerapps-docs/maker/data-platform/azure-synapse-link-transition-from-FnO.md

@@ -185,7 +185,7 @@ If you're consuming incremental data feeds from Dynamics 365 with Export to Data
 
 ## Known issues and workarounds
 
-Currently, there are several limitations that are being addressed by the product team. Until we fix these limitations, use the suggested workaround. To learn more about the upcoming roadmap and stay in touch with the product team, join the preview [Viva Engage group](https://akamms.SynapseLinkforDynamics).
+Currently, there are several limitations that are being addressed by the product team. Until we fix these limitations, use the suggested workaround. To learn more about the upcoming roadmap and stay in touch with the product team, join the preview [Viva Engage group](https://aka.ms/synapselinkfordynamics).
 
 |Known issue |Fixes and Workarounds |
 |---------|---------|
@@ -194,8 +194,8 @@ Currently, there are several limitations that are being addressed by the product
 | In case your Dataverse environment is located in an Azure region different than the one where your Fabric capacity is located, you can’t use the **Link to Fabric** feature. | As of April 30, 2024, you can link to a Fabric capacity located within the same geographic boundary, such as United States. <br><br> Notice that you might incur networking charges in Fabric due to data transfer between Azure regions. |
 | In case your Dataverse environment is located in an Azure region different than the one where your data lake or Synapse workspace is located, you can’t use the Azure Synapse Link feature. | As of April 30, 2024, you can link to a storage account located within the same geographic boundary, such as United States. <br><br> Notice that you might incur networking charges in Azure resources like data lakes if they aren't located within the same Azure region. |
 | AOS authorization is a way to secure sensitive data fields in finance and operation apps against data exfiltration scenarios. <br> If the table selected contains data columns that are secured via AOS authorization, those columns are ignored and the exported data doesn't contain the column. <br><br> For example, a custom table column *TaxLicenseNum* has the metadata property `AOS Authorization` set to **Yes**. This column is ignored | Update your finance and operations environment to these versions or later: <br>- PU 63:7.0.7198.105 <br>- PU 62:7.0.7120.159 <br>With this update, AOS authorization fields are added to tables. <br>- Incremental updates include this column. <br> -	Modified records show these columns and value. <br> -	Full refresh includes these fields and all values. |
-| If the table selected contains data columns that are of **Array** type, those columns are ignored and the exported data doesn't contain the column. <br><br>For example, in a custom table named *WHSInventTable*, columns `FilterCode` and `FilterGroup` are of type array. These columns aren't exported with Azure Synapse Link. | There's no workaround to this issue. We're working to enable this feature in a future update. <br><br> Join [Viva engage group](https://aka.ms./synapselinkfordynamics) to stay in touch and onboard preview features when available. |
-| In case of finance and operations apps tables that exhibit [valid time stamp behavior](/dynamicsax-2012/developer/valid-time-state-tables-and-date-effective-data), only the data rows that are currently valid are exported with Azure Synapse Link. <br><br> For example, the `ExchangeRate` table contains both current and previous exchange rates. Only currently valid exchange rates are exported in Azure Synapse Link. | As a workaround, until this issue is fixed, use a table such as **ExchangeRateBIEntity**. <br>Join [Viva engage group](https://aka.ms./synapselinkfordynamics) to stay in touch and onboard preview features. |
+| If the table selected contains data columns that are of **Array** type, those columns are ignored and the exported data doesn't contain the column. <br><br>For example, in a custom table named *WHSInventTable*, columns `FilterCode` and `FilterGroup` are of type array. These columns aren't exported with Azure Synapse Link. | There's no workaround to this issue. We're working to enable this feature in a future update. <br><br> Join [Viva engage group](https://aka.ms/synapselinkfordynamics) to stay in touch and onboard preview features when available. |
+| In case of finance and operations apps tables that exhibit [valid time stamp behavior](/dynamicsax-2012/developer/valid-time-state-tables-and-date-effective-data), only the data rows that are currently valid are exported with Azure Synapse Link. <br><br> For example, the `ExchangeRate` table contains both current and previous exchange rates. Only currently valid exchange rates are exported in Azure Synapse Link. | As a workaround, until this issue is fixed, use a table such as **ExchangeRateBIEntity**. <br>Join [Viva engage group](https://aka.ms/synapselinkfordynamics) to stay in touch and onboard preview features. |
 |[Table inheritance and derived tables](/dynamicsax-2012/developer/table-inheritance-overview) are concepts in finance and operations apps. When choosing a derived table from finance and operations apps, columns from the corresponding base table currently aren't included. | You need to select the base table in addition to the derived table if you need access to these columns. <br> You can use [this FastTrack solution provided via GitHub](https://github.com/microsoft/Dynamics-365-FastTrack-Implementation-Assets/tree/master/Analytics/DataverseLink/DataIntegration#derived-tables). This solution creates views, which include columns from base tables. |
 | Export more than 1,000 tables via Azure Synapse Link or add more than 1,000 tables to Fabric link. |  If you're using Azure Synapse Link, work around this issue by creating two or more profiles that contain less than 1,000 tables. <br><br> Expect to select more than 1,000 tables in Fabric Link and in an Azure Synapse Link profile in a future update.| 
 | Finance and operations apps tables included in an Azure Synapse Link profile can't be migrated to a different environment using the import and export profile feature in Azure Synapse Link. | Until this issue is addressed, add the same tables into the new environment. Copy and paste a comma separated list of tables into the search box within the manage tables option to select a list of tables at once.  |