- Newest
- Most votes
- Most comments
As of now, AWS WorkSpaces Pools does not support using AWS Managed Microsoft AD for authentication. WorkSpaces Pools currently only supports Security Assertion Markup Language 2.0 (SAML 2.0) for user authentication.
You're correct that WorkSpaces Personal can use AWS Managed Microsoft AD for authentication. However, for WorkSpaces Pools, SAML 2.0 is the only supported authentication method at this time.
Unfortunately, there is no publicly available information about whether AWS has plans to add support for AWS Managed Microsoft AD in WorkSpaces Pools. AWS typically doesn't disclose their product roadmaps publicly.
If using the same directory for both WorkSpaces Personal and WorkSpaces Pools is crucial for your use case, you might want to consider reaching out to AWS support or your AWS account representative to express your interest in this feature. They may be able to provide more information or pass along your feature request to the appropriate team.
In the meantime, if you want to use WorkSpaces Pools, you would need to set up SAML 2.0 authentication. This would allow you to use features like pay-as-you-go pricing and shared desktop pools, but it would require a different authentication setup from your existing WorkSpaces Personal environment.
Sources
User connections to WorkSpaces Pools - Amazon WorkSpaces
Integrate SAML 2.0 with WorkSpaces Personal - Amazon WorkSpaces
Announcing Amazon WorkSpaces Pools, a new feature of Amazon WorkSpaces - AWS
answered 2 years ago
WorkSpaces Pools only support SAML 2.0 identity providers (IdPs).
To use AWS Managed AD with Pools, you can setup a SAML 2.0 provider with Active Directory Federation Services (AD FS).
The blog AWS Federated Authentication with Active Directory Federation Services (AD FS) can help with setup.
Relevant content
asked a year ago
asked 9 months ago
asked 2 years ago
