Forum Discussion
MSIX and AADDS support
As stated in the FAQ section, MSIX app attach and AADDS cannot work together due to the missing sync of computer objects from AADDS to AAD.
Is there a way to bypass this limitation, or perhaps it is on the backlog to get fixed? Syncing computer objects was never a problem before with the sync service?!
I really want to do PaaS and not fall back to building an ADDS Forest with AAD Connect in Azure.
ty
Paul Slijkhuis this is a highly needed and desired feature and certainly being worked on by the Product Group. Particularly we introduced Azure AD join for AVD VMs. That also poses some challenges with accessing Azure File Shares with regards to the lack of Kerberos Authentication. Of course like you mentioned the Machine Accounts are key for MSIX so that will likely be part of the solution when it comes out. Not ETA as of yet, but certainly something that is likely on the Product Group's high priority list.
Some of our customers have actually resorted to using NetApp File Shares, albeit more expensive, to overcome this issue as well. If you already have NetApp File Shares that may be an option in the interim.
So stay tuned, it is definitely something in the works to be solved by the Azure Product Group sooner than later!
1 Reply
- Jonathan1095
Microsoft
Paul Slijkhuis this is a highly needed and desired feature and certainly being worked on by the Product Group. Particularly we introduced Azure AD join for AVD VMs. That also poses some challenges with accessing Azure File Shares with regards to the lack of Kerberos Authentication. Of course like you mentioned the Machine Accounts are key for MSIX so that will likely be part of the solution when it comes out. Not ETA as of yet, but certainly something that is likely on the Product Group's high priority list.
Some of our customers have actually resorted to using NetApp File Shares, albeit more expensive, to overcome this issue as well. If you already have NetApp File Shares that may be an option in the interim.
So stay tuned, it is definitely something in the works to be solved by the Azure Product Group sooner than later!