Mark Duff

My feedback

  1. 12 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mark Duff commented  · 

    This same issue is spread among multiple comment threads, which dilutes our true fury over the arbitrary removal of SSMS diagrams (which should also have been in VS long ago). How many of we who have paid for it for years requested this? What exactly was the Use Case?

    Where is the sense of urgency in the midst of effectively destroying decades of architectural drawings caused by simply not including something that's always worked fine the the past?

    https://feedback.azure.com/forums/908035-sql-server/suggestions/37992649-ssms-18-1-crashes-when-opening-a-database-diagram

    Mark Duff supported this idea  · 
  2. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mark Duff commented  · 
    Mark Duff supported this idea  · 
  3. 13 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    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?

    Thanks,
    -Matteo

    Mark Duff supported this idea  · 
    An error occurred while saving the comment
    Mark Duff commented  · 

    As others have mentioned, I am master of my domain in Azure A. I am an elevated guest and AAD Directory Admin for the DB Server in Azure B. I receive this error when 1st login to the DB Server in Azure B while logged into everything, including SSMS as myself in Azure A.

    I could create an elevated User in Azure B used exclusively for SSMS connection. But doesn't that pretty much defeat the "S" in "SSO"?

  4. 1,173 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    627 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Duff supported this idea  · 
  5. 1,571 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  174 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Duff supported this idea  · 
  6. 1,398 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    81 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →

    We definitely recognize the popularity of this feature, and we discuss it constantly during the planning phases. However there are certain technical limitations in the system that add a large amount of development cost. Because of the cost and the fact that there is a workaround available, other features get prioritized over this one.

    That being said, please keep voting for it. The popularity of the feature does help bring it up and makes us reconsider every time.

    Apologies for the delay.

    /Parakh


    Old message:
    We’re doing some research both on the specifics of this ask as well as what it would take to support this.
    Is the ask here to do the same thing that regular Azure AD does (see: https://blogs.technet.microsoft.com/enterprisemobility/2014/12/18/azure-active-directory-now-with-group-claims-and-application-roles/) or is are there different requirements around this for Azure AD B2C?

    An error occurred while saving the comment
    Mark Duff commented  · 

    How is this even a disconnect? Every MS Evangelist recommends, nay, insists, nay admonishes us if we don’t base authorization on AD Groups rather than Users. But B2C AD User’s Groups are hidden from simple Claims? MS says, “oh, it’s too much work”. Not for your competitors. You want their slice of the pie? After years of waiting for this, it seems not. Our inability to recapture in Claims transitions from B2C casual visitors (Group) to prospects (Group) to customers (Group) to heightened elevations w/o our own mechanisms renders B2C AD Grouping moot and negates all the other relevant MS preaching. Really MS? We who work quietly ARE your true evangelists. But this is a sad sacrifice of a tree that makes the forest.

Feedback and Knowledge Base