I’m receiving the following error when I try to login in the Amazon Quick for Desktop in a Windows machine: “Enterprise sign-in for Quick Desktop has not been configured for this account. Contact your IT team for further support.”
I’m assigned with an admin pro license and today all the capabilities are enabled in my account:
The error Enterprise sign-in for Quick Desktop has not been configured for this account indicates that enterprise SSO (Single Sign-On) / IdP federation has not yet been configured for the Quick Desktop application at the account level. This is a separate configuration step from user licensing and capabilities, and it typically needs to be completed by your IT administrator.
Go to the QuickSight web console → click your profile icon (top right) → Manage QuickSight
Navigate to Single sign-on (IAM federation)
Provide the IdP URL and relay state parameter
Set the Status to ON
If using IAM Identity Center: Verify that the QuickSight application is registered in IAM Identity Center and that your user or group is assigned to it.
If everything looks correct and SSO appears to be properly configured and you’re still seeing this error, open an AWS Support ticket, it may be a provisioning issue on the backend. Here are the steps to open a support case.
Same issue here. My account is correctly configured per documentation: AuthenticationType=IAM_IDENTITY_CENTER, Edition=ENTERPRISE, in us-east-1, IAM Identity Center instance linked, my user assigned as Admin Pro to the Quick application with all capabilities enabled. Validated via describe-account-subscription API. Account was created prior to the Desktop preview launch. Looks like a backend provisioning gap for pre-existing accounts.
If everything looks correct and SSO appears to be properly configured and you’re still seeing this error persist. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!