We have completed according to the document guide Setting up Amazon Quick on desktop for enterprise deployments - Amazon Quick . We linked MS Entra ID with AWS Identity Center and AWS IdC with Quick extension as screenshot above.
When user log in, it does transfer us to the MS portal but after successfully log in, the screenshot say that Quick Desktop has not been configured even though we completed the extension already.
Would be very appreciated if anyone could provide us any support.
Hi Khang
I have the same situation as you’ve described.
The documentation you linked to, describes setting up the “Trusted Token Issuer” setup (in part 4 of step 3). However, that screen is tucked away in the Teams module, which I think is a bug.
Were you able to carry out that step?
Hi - I have an update for you after a long call with AWS support!
Turns out there’s another, undocumented, place where you have to enable the extension.
As your Quick User (not in the admin part) you need to click Extensions:
You’ll see the Office extensions, etc. Click “Create Extension” and here you’ll see the Quick Desktop extension (which you previously set up following the admin guide you linked to).
Once I’d added that, I was able to sign in with Amazon Quick Desktop.
Thanks Tom,
We have enable Desktop extension on user side. However, the callback from SSO does not seem to work. I have verified that
Much appreciated if anyone could support on this!
I’m facing the same issue, not being able to use Quick Desktop with SSO Login.
I tried @Tom_Kerswill suggestion, but on eu-central-1 region, I cannot see the “Create Extension” button, logged in with an admin user:
Hi - I am pretty sure Quick Desktop only supports us-east-1 region.
If you use Amazon Identity Centre, that also needs to be in us-east-1.
Ours was in eu-west-1. However, we were able to use the new replication feature to replicate to us-east-1, and this did work. There’s a bit of work involved; but if you a) replicate Identity Center to us-east-1 and b) create Amazon Quick in us-east-1 (we had to use the CLI to do this - the web GUI was hardwired to our home region) and c) do the things mentioned in our post above, then hopefully you’ll find this works!
Just in addition to this, you do also have to make sure your Quick user is in the admin group.
Hi @Khang_Nguyen,
Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.
Thank you
Hi @Khang_Nguyen ,
Since I haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.
Thank you
