Sorry folks, but we are not able to repro this issue (either using SSMS 17.9.1 or SSMS 18 Preview 7).
Since multiple people out there are reporting this issue, it is obvious that we are missing something that is specific to your environment or configuration.
Could you help us out and try to describe a little better your subscription/environment/account/permissions?
For example, does the following mainstream scenario works for you all:
1) Connect to Azure Portal
2) Create SQL server+database
3) Go to SSMS and connect to
4) Add firewall rule
If it does, then can you identify what is different between the case where it works and the case where it does not?
-MatteoJoel supported this idea ·
An error occurred while saving the commentJoel commented
The issue happens when database is on Tenant B and user is guest from Tenant A.
DB on Tenant A and User on Tenant A works fine.
So it is most likely a B2B related issue.