# Issue with Comment Edit Synchronization between Jira Cloud and Azure DevOps Cloud **URL:** \ **Category:** General Questions\ **Tags:** azuredevops-jiraclou\ **Created:** [June 30, 2025, 9:11am UTC](https://community.exalate.com/t/issue-with-comment-edit-synchronization-between-jira-cloud-and-azure-devops-cloud/6496 "2025-06-30T09:11:49Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Jillani\_Fazal](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/jillani_fazal/32/355_2.png) [@Jillani\_Fazal](https://community.exalate.com/u/Jillani_Fazal)\ **Post date:** [July 7, 2025, 8:29am UTC](https://community.exalate.com/t/issue-with-comment-edit-synchronization-between-jira-cloud-and-azure-devops-cloud/6496/6 "2025-07-07T08:29:55Z")
Hi Angel, Thank you for the poke. 🙂 I will be working on it and will get back to you. In the meantime, please check this and let me know it this one serves the purpose? > [@Exalate - Azure DevOps Restrict Comment Editing](https://community.exalate.com/t/exalate-azure-devops-restrict-comment-editing/6442): > > We’re looking to optimize our Exalate synchronization in Azure. We’ve heard that adjusting sync behavior to only create new comments (and avoid editing existing ones) is generally the safest and most scalable approach. For those of you using Exalate in Azure, what user are you typically leveraging for your Exalate integration, and have you found this ‘new comment only’ sync strategy to be effective in your environment? Any insights or best practices regarding user permissions or sync configura… --- _[View the full topic](https://community.exalate.com/t/issue-with-comment-edit-synchronization-between-jira-cloud-and-azure-devops-cloud/6496)._