Microsoft
MicrosoftHi jheim1215, thanks for the additional context.
The link to the feedback site is in the post, but sharing it again here:
https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0
Within SSMS, if you go to Help | Technical Support, it also takes you to the site.
To find issues related to SSMS, you can filter to Tooling (select See All under Groups to find that checkbox) and then in the search bar, enter a phrase or just SSMS. I typically order issues from newest to oldest and work backwards.
In order to upvote, you have to be logged in (icon in the upper right), once you have an issue selected, on the bottom right, just below the issue text is an up arrow, with text to the right listing the number of votes it has.
The issue you noted for Azure SQL Managed Instance when viewing properties is known and documented in the release notes (https://learn.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-ver16#bug-fixes-in-191). This is a bug in the engine, not in SSMS, and it has been reported and will hopefully be fixed soon.
For the replication issue you mentioned with Managed Instance, I don't see anything for that on the feedback site, nor do I see that we have anything logged internally. I will find some time to verify (thank you for providing the steps to recreate) and assuming I can recreate it, will log an issue for the team.
I am not familiar with POORSQL, but as noted in my previous comment, extensions are developed by third-party companies or individuals. There are changes between major releases (18.x to 19.x) and because folks don't have access to the SSMS code base, they can only begin to work on an update after the release becomes available. Depending on changes, their availability, and their ability to do testing, it may be difficult to keep up.
Appreciate the clarification, no hard feelings. I agree: Microsoft has changed direction on key products in the past. I understand why one might think that ADS competes with SSMS - that's on me to make the vision and value for each tool better known to our users. There's nothing to infer in the release pattern. Whenever there is a major box release of SQL, like SQL Server 2022, we have a new version of SSMS to support it (SSMS 19.x). The next set of changes we are making for SSMS, which are independent of box release, are significant and require a version bump to SSMS 20. No hidden agenda, just the way releases go.
Hope this clarifies any remaining concerns, but please let me know if there's anything else with which I can help.