First of all Thanks for your quick response. :)

after your suggestion i switch to edge browser and use private window then login my github account then redeem my azure benefit still have same issue.
Browser: edge
OS: Windows 10
DNS/ automatically then use google DNS still facing same issue
extensions: None

Also switched my internet connection on the laptop WiFi to mobile data still same issue

Thanks for the update, and also for testing everything so thoroughly.
Your explanation actually makes it much clearer what is going on.

From what you described, this is the same issue that has been affecting some Azure Student accounts recently. The verification step is supposed to load an interactive button from Arkose Labs, but on certain systems the script never renders the button. That is why the page shows the message asking you to press and hold, but gives you nothing to click. Since you already tested multiple browsers, private windows, DNS changes and even a different network, this strongly points to an Azure side problem rather than anything related to GitHub.

There is one workaround that has helped a lot of students who had the same problem. If you have not tried this specific path yet, start the process from the Student Pack page instead of the usual login screen:

https://azure.microsoft.com/free/students/?WT.mc_id=studentbenefits

Open this page in a private window, choose the option to continue with GitHub, and try the process there. This route often forces Azure to load the older verification flow, which does not rely on the failing widget.

If the button still does not appear even through this entry point, then your plan to contact Azure support is the correct next step. They can reset the verification challenge or move your account to the fallback flow manually.

If you manage to resolve it, please share what worked. It will definitely help other students who run into the same issue.

Hello @muratalpaslan,

Thanks again for looking into this. I really appreciate the detailed guidance.

I tried the link you shared, but unfortunately the issue is still the same. I do have one more question: what happens if I skip the “Start free” button under the student offer and instead use the “Sign in” button at the top right? This is the only path I haven’t tested yet.

If I sign in that way, will Azure still recognize my email as a verified GitHub Student Developer Pack account, or could it cause any issues with the student benefits ? If you have any insight on this please let me know.

Thanks again for your help.!!!

Hello @muratalpaslan,

Thanks again to explain further!!!

I just try login again with "start free" and this time it took me to verification captcha not that "Ghost Button" :P I solved the captcha then it took me further where it showed me same window with "NEXT" button I proceed to next then it took me to the window where it showing me this msg

[Microsoft-> My Email ID-> create account ]

just stuck here, I guess this temporary issue from azure and it will resolve soon i think they're working on it that's why now i can see the captcha this time.

previous image
I
I

This is just a light heart joke----> Now I know why Bill Gates got divorced from his wife it's not about personal problems it's all about the "Captcha" even she did the right microsoft reject she had no option. :P :D :D

Hello again, and thanks for the new screenshots. They actually helped a lot. I can see the screens you shared, and they confirm what I suspected earlier.

When Azure shows your email followed by “Create account”, it means the onboarding flow is not linking your GitHub-verified student status to an existing Microsoft identity. Instead, Azure tries to create a brand new Microsoft account for that email. This only happens when Azure cannot retrieve the verification token it expects from GitHub, even though your student status is valid. So the handoff between GitHub and Azure is failing in the background.

This explains why you have been seeing different behaviour each time. First the verification button was missing, then the captcha appeared, and now the system is falling back to “Create account”. This usually happens during Azure maintenance or backend updates. The flow becomes inconsistent until the service stabilises.

There are only two reliable ways to move past this point.

The first option is signing in with a Microsoft account you already have. If you use the sign-in button at the top right and log in with any existing Microsoft identity you own, Azure will attach your GitHub student verification to that account. This avoids the “Create account” loop entirely because Azure no longer has to create a new identity during the process.

The second option is to wait and retry later. When Azure is updating the Student offer backend, this exact behaviour appears very often. The flow jumps between multiple screens because parts of the service are being rolled out or restarted. Once the updates settle, the flow usually works properly again, and Azure is able to link your GitHub student token without asking you to create a new account.

You also do not need to worry about losing your student benefits. Signing in from the top right will not affect your eligibility or your GitHub verification. Once Azure is able to complete the identity link, your student credits will activate normally.

If you try signing in with an existing Microsoft account and it behaves differently, feel free to share what you see. You are already much closer than before, especially now that the captcha is loading. I am happy to help until everything goes through smoothly.

Hello @muratalpaslan,

Thank you once again for all your help your detailed guidance has been extremely useful.

I just checked the “Sign in” option as well, and it’s showing the same issue as “Start free.” It seems your earlier prediction was correct: this might be one of those Azure-side problems that resolves only after a few days once their updates settle. That approach feels safer than repeatedly trying the verification flow.

I’ll wait a few days and try again once things are more stable. If the issue still appears after that, I’ll reach out again.

Thank you very much for your thorough analysis and support throughout my troubleshooting.

Thanks for the update, I really appreciate that you took the time to test both flows.

Waiting a few days is definitely the right move here - Azure verification issues like this usually settle once their backend updates finish propagating. When everything stabilizes, the captcha widget and the “Next” step should behave normally again.

If the verification still fails after a few days, feel free to share a screenshot or describe the exact step where it gets stuck. I’ll gladly take another look and help you narrow it down further.

Glad I could assist - hope the next attempt goes smoothly.

Hello @davevad93,

Yes I'm a verified student with student developer pack.

It seems like the issue isn’t related to the GitHub ticket itself, but specifically to Azure’s human verification widget. I’ve tried multiple browsers chrome, firefox, edge, opera including fresh installs with no extensions or add-ons, and even used private/incognito mode. I was able to log in and redeem the Azure benefit, but the verification widget still doesn’t display any interactive button.

At this point, it appears to be an Azure-side problem. I’ll reach out to Azure support and update once I hear back.

You're welcome @Pratyush56555. Yes, you have to reach out to Azure support and ask for assistance.