A cloud-based identity and access management service for securing user authentication and resource access
Hello Mohammad Aman Ansari,
Greetings! Thanks for raising this question in the Q&A forum.
The error you're seeing, AADSTS50058: A silent sign-in request was sent but no user is signed in, is almost always a browser session/cookie issue rather than a missing Entra ID permission. Azure AD tries to silently re-authenticate you using existing session cookies, and when those cookies are blocked, stripped, or associated with a different (unexpected) account, this error is thrown before the App Registrations page ever loads. This happens even to accounts that have full Global Administrator or Application Developer rights, so the fact that you're hitting this error doesn't by itself mean your account lacks permission.
Please try the following steps in order:
Rule out multiple signed-in accounts Go to https://myaccount.microsoft.com and check if more than one Microsoft account (personal or work) is cached in the browser. If you see multiple accounts, sign out of all of them completely, close the browser, then sign back in with only the @shadbox.in work account.
Check third-party cookies and browser extensions The AADSTS50058 error is frequently caused by third-party cookies being blocked or an ad blocker/privacy extension interfering with login.microsoftonline.com. Temporarily disable all browser extensions and enable third-party cookies for *.microsoftonline.com and *.microsoft.com, then retry.
Test with a different browser and network Try a completely different browser (not just an Incognito window in the same browser, since some extensions still run there) and, if possible, a different network. Corporate VPNs, proxies, and firewalls can strip session cookies before they reach Azure AD, which produces exactly this error.
Try direct navigation instead of a bookmarked/cached link Navigate directly to:
https://entra.microsoft.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
instead of using a saved link, since stale cached redirect URLs can also trigger silent sign-in loops.
Confirm the account actually has the required role Once you can reach the Entra admin center, go to Identity > Roles and administrative units > Application Developer (or check if you already hold Cloud Application Administrator or Application Administrator). By default, all users in a tenant can register applications unless this has been restricted at Identity > Users > User settings > App registrations > Users can register applications. If that setting has been switched to No, ask your tenant administrator to either enable it or assign you the Application Developer role directly.
Check for Conditional Access policies If your tenant admin has Conditional Access enabled, ask them to check Identity > Protection > Conditional Access > Sign-in logs filtered to your user and correlate the timestamp of the failure. A policy requiring a compliant device, MFA, or a specific network location can also produce a login loop that surfaces as this error if a condition silently fails.
If none of the above resolves it, please collect the Correlation ID, Request ID, and Timestamp shown in the full error details (visible if you click "See error details" or check the URL parameters) and open a support ticket with Azure Support under Microsoft Entra ID > Sign-in / authentication issues, since a tenant-side session or Conditional Access misconfiguration will need to be checked from the backend.
If this answer helps you kindly accept the answer which will help others who have similar questions.
Best Regards,
Jerald Felix.