Product Feature Differences in Version 7 between Active Directory and Entra ID for User Directory
This is a list of the key product feature differences when deploying MyWorkDrive on a domain-joined server with Active Directory for user database/identity vs a standalone server using Entra ID for identity. Features not listed here are equivalently available in either configuration.
Feature | Active Directory | Entra ID |
---|---|---|
User Database / Access | Active Directory, via LDAP | Entra ID via GraphAPI |
Server Computer Account | Must be Windows domain-joined | No Domain Required |
Windows File Share Access | via SMB and NTFS in the User Context | Uses a Service Account |
Azure File Share | via SMB or Connection String | via Connection String or Entra ID |
Azure Blob Storage | via Connection String | Via Connection String, Entra ID, Entra ID with Hierarchal Namespace |
Managed Identity for Azure VM | Not Supported | With Entra ID Auth for Blob and Azure File Share - Preferred Method |
MFA | Native with Duo or as Configured in SSO Provider | Native in Microsoft Log in |
SSO Sign in | via SAML | Native Microsoft Log in |
User/Pass Sign in | Optional with Domain Credentials | Not Available |
Clustering of Config Files | Optional via SMB Storage | Not Currently Available (In Development) |
Guest User via Microsoft B2B | MyWorkDrive Guest User Access Process | Natively Microsoft Guest User in Entra ID |
WevDAV | Optionally available | Not Available |
Teams Client | Optionally Available | Not Available |
File and Folder Level Permissions | NTFS Permissions via SMB | ACL via Azure Blob with Hierarchical Namespace |
Search | Windows Search Service, dTSearch | Not Available |
File Locking | Applied on SMB, Internal to MyWorkDrive for Other Storage Types | No External Locks are Applied. Locks Exclusively Internal to MyWorkDrive |
We appreciate your feedback. If you have any questions, comments, or suggestions about this article please contact our support team at support@myworkdrive.com.