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 stand alone 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 namespac |
| 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 Login |
| SSO Sign In | via SAML | Native Microsoft Login |
| 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.