In its own way, "these Settings you can only get to by opening a web browser and going to account.microsoft.com" is just as bad as "these Settings you can only

In its own way, "these Settings you can only get to by opening a web browser and going to account.microsoft.com" is just as bad as "these Settings you can only get to by finding them in an older Control Panel", isn't it? Even assuming it is "zero sum" that this Settings page took resources away from other Settings migrations, it's still a net win for "Settings all in one place" isn't it? (In which the article also points out is unlikely to be a "zero sum" case here, because the whole point of using React Native is so that the team that is in charge of "account.microsoft.com" directly can own the Settings page and can share code in it with what they also run on account.microsoft.com. It seems highly unlikely that that web-based team has any other older Control Panel they "own", and more likely that if they own their own Settings page that a team that does own older Control Panels and new Settings pages doesn't have to "moonlight" or "hand hold" the web team's Settings work.)