link

fixed

Author: vac0224

articles/communication-services/concepts/chat/concepts.md

@@ -40,7 +40,7 @@ Azure Communication Services supports three levels of user access control, using
 ### Chat Data 
 Azure Communication Services stores chat threads according to the [data retention policy](/purview/create-retention-policies) in effect when the thread is created. You can update the retention policy if needed during the retention time period you set. After you delete a chat thread (by policy or by a Delete API request), it can't be retrieved.
 
-[!INCLUDE [public-preview-notice.md](../includes/public-preview-include-document.md)]
+[!INCLUDE [public-preview-notice.md](../../includes/public-preview-include-document.md)]
 
 You can choose between indefinite thread retention, automatic deletion between 30 and 90 days via the retention policy on the [Create Chat Thread API](/rest/api/communication/chat/chat/create-chat-thread), or immediate deletion using the APIs [Delete Chat Message](/rest/api/communication/chat/chat-thread/delete-chat-message) or [Delete Chat Thread](/rest/api/communication/chat/chat/delete-chat-thread). Any thread created before the new retention policy isn't affected unless you specifically change the policy for that thread. If you make a support request after your data retention policy time period has passed, the chat thread can no longer be retrieved.