
Generic Accounts: Microsoft's licensing terms generally discourage the use of shared or generic accounts for multiple users. Each individual user should have a unique user ID, primarily for compliance, security, and licensing reasons.
Windows E3/E5 Licenses: Windows E3/E5 licenses are per-user licenses. This means they are assigned to individual users and allow the licensed user to access the service from any device. If you're using generic accounts, this licensing model could pose a problem since it would be challenging to determine which user is accessing the VDI at any given time.
VDI per Device Licenses: This model licenses the device rather than the user. If Organization B intends to use VDI per Device licenses, they should ensure that each device accessing the VDI has a license. However, remember that the concept of "generic accounts" is still problematic.
Licensing Hierarchy: Generally, if a user from Org A has a higher-tier license than the generic account, they technically have access to the features of the lower-tier license. However, this doesn't solve the problem of using generic accounts, which is the core of the issue.
Licensing Across Organizations: If a user from Org A is accessing resources in Org B, the license for accessing those resources should ideally be provisioned by Org B, especially if they're using Org B's infrastructure and services. While the user's license from Org A might technically allow them access to certain features, it may not be compliant for them to access another organization's resources without the appropriate licenses from that organization.
best regards,
iohann gessenay