Update known-issues.md

Author: EXPEkesheth

articles/healthcare-apis/known-issues.md

@@ -20,8 +20,8 @@ Refer to the table for details about resolution dates or possible workarounds.
 
 |Issue | Date discovered | Workaround | Date resolved |
 | :------------------------------------- | :------------ | :------------- | :------------- |
-|Changes in private link configuration at the workspace level do not propagate to the child services. Even with Private Link set at the workspace level, an account has its traffic manager set to use public endpoints, instead of private endpoints.|September 4,2024 9:00 am PST| To fix: a service reprovisioning is required to "wake up" the service for the new configuration. Reach out to FHIR service team to reprovision the service|--|
-|Customers accessing the FHIR Service via a private endpoint are experiencing difficulties, specifically receiving a 403 error when making API calls from within the vNet. This problem affects those with FHIR instances created post-August 19th that utilize private link.|August 22,2024 11:00 am PST|Suggested workaround to unblock is - Create a Private DNS Zone for azurehealthcareapis.com under the same VNET and then create a new recordset to the targeted FHIR service. | September 3.2024 9:00 am PST|
+|Changes in private link configuration at the workspace level don't propagate to the child services.|September 4,2024 9:00 am PST| To fix this issue a service reprovisioning is required. To reprovision the service, reach out to FHIR service team|--|
+|Customers accessing the FHIR Service via a private endpoint are experiencing difficulties, specifically receiving a 403 error when making API calls from within the vNet. This problem affects FHIR instances provisioned after August 19th that utilize private link.|August 22,2024 11:00 am PST|-- | September 3.2024 9:00 am PST|
 |FHIR Applications were down in EUS2 region|January 8, 2024 2 pm PST|--|January 8, 2024 4:15 pm PST|
 |API queries to FHIR service returned Internal Server error in UK south region |August 10, 2023 9:53 am PST|--|August 10, 2023 10:43 am PST|