Mark Hildreth
My feedback
-
1,337 votes236 comments · Azure Active Directory » End user experiences · Flag idea as inappropriate… · Admin →
Folks,
Thanks for the questions and suggestions. And apologies for not sharing any update on this thread for so long. We’ve been working on this problem and have announced changes on our official team blog (see here: https://cloudblogs.microsoft.com/enterprisemobility/2016/09/15/cleaning-up-the-azure-ad-and-microsoft-account-overlap/).
First, we are acutely aware of the UX pain this is causing and we are sorry for this. We are trying to undo a decade and a half of systems divergence. There are literally hundreds of different engineering teams across Microsoft involved in this effort. So this is taking time.
Second, we can’t easily “merge” two accounts, or allow IT to “take over” personal Microsoft accounts. There are two main hurdles: (1) The terms of service are fundamentally different for the two account types and (2) they are based on different technologies with different stacks (different identifiers, SDKs, token formats, etc.). We’re working to converge the two stacks but again this…
An error occurred while saving the comment Mark Hildreth
supported this idea
·
-
900 votes
Good feedback. No plans in this area, yet.
Mark Hildreth
supported this idea
·
-
1,173 votes
We are likely to support this in phases. Stay tuned for more details.
Mark Hildreth
supported this idea
·
-
932 votes
A common need for users of Azure Table Storage is searching data in a Table using query patterns other than those that Table Storage provides efficiently, namely key lookups and partition scans. Using Azure Search, you can index and search Table Storage data (using full text search, filters, facets, custom scoring, etc.) and capture incremental changes in the data on a schedule, all without writing any code. To learn more, check out Indexing Azure Table Storage with Azure Search: https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-tables
Mark Hildreth
supported this idea
·
-
1,708 votes
This work is on our backlog and currently under consideration. We will update here if this changes.
Mark Hildreth
supported this idea
·
I totally agree. We created a Microsoft account (admin@company.com) so that we could create Windows Azure subscriptions. We then we've adopted Office 365, creating an account using that Microsoft account. We set up dir sync (to Office 365) thinking this would allow us to give our staff access to the Azure subscriptions using their sync'd accounts, but we are left with two disparate AD tenants: one of Office 365 (sync'd) and one under the Microsoft account (not sync'd).