hi surbhi! ))
aha, i see whats happening here.... first, about the admin credentials, those fields for clientsecret and secret token can be tricky. make sure ure copying the entire value from aws. no extra spaces, no missing characters. sometimes the cursor plays tricks and cuts off part of the token. double… no, triple check that ))
if u still hitting save and nothing happens, refresh the page (old school lol but works). clear ur browser cache or try incognito mode. microsoft docs actually mention this can help when things get stuck. if ur using a vpn or corp network, switch it off temporarily. some policies block api connections.
now, about provisioning status should appear under the 'monitor' tab once u save the credentials. but if its ghosting u, go to 'provisioning logs' instead. it’s kinda the backstage area where u can see if microsoft entra is even trying to talk to aws. look for errors like 'invalid credentials' or connection timeout. if u havent already, make sure the aws iam role has these exact permissions listed in the docs. missing one = instant fail.
still no luck? hit 'test connection' first before saving. if that passes but save doesn’t work, its 100% a ui glitch. microsoft’s end might just need a kick, wait an hour or try again tomorrow. their servers get moody sometimes :))
ps: love that u followed the docs! they’re gold but yes agree, some steps age like milk. here’s the link again if u need it microsoft entra aws tutorial.
keep me posted! %)
Best regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment