Domain-Joined AppStream 2.0 Streaming Instances
SAML 2.0-based user federation is required for application streaming from domain-joined Always-On and On-Demand fleets. You cannot launch sessions to domain-joined instances by using CreateStreamingURL or the AppStream 2.0 user pool.
Also, you must use an image that supports joining image builders and fleets to an Active Directory domain. All public images published on or after July 24, 2017 support joining an Active Directory domain. For more information, see AppStream 2.0 Base Image and Managed Image Update Release Notes and Tutorial: Setting Up Active Directory.
Note
You can only join Windows Always-On and On-Demand fleet streaming instances to an Active Directory domain.