azure session loop

Hello pat donnelly, Thanks for reaching out on Microsoft Q&A and really appreciate your patience while we looked into this.
The core issue is that your browser is holding on to a piece of old or conflicting information (a session token or cookie) from a different Microsoft service, and the Azure portal's sign-in process is rejecting it, leading to the "Session Expired" error loop.

Let's Narrow Down the Root Cause
To get a complete picture and provide the most accurate solution, please consider answering the following questions:

1. Account Type: Are you using a personal Microsoft account (e.g., @outlook.com) or a corporate/managed work account (e.g., @yourcompany.com)?
2. Device Management: Is this PC managed by your organization (e.g., via Intune, Group Policy, etc.)?
3. Network Configuration: Are you behind a corporate VPN, proxy, or any firewall appliance that might be inspecting or altering network traffic?
4. Browser Extensions: Do you have any browser extensions installed, especially security-related ones like Adblockers, cookie managers, or privacy extensions?
5. Time and Date: Can you confirm that your PC's date and time are set correctly and are synchronized automatically via the internet?
6. Alternative Test: Have you tried logging into portal.azure.com from a different web browser (e.g., Chrome or Firefox) or on a different device (like a mobile phone) to see if the issue persists?

-Suggested Solutions (Step-by-Step)

Based on the information you've provided, let's try a few more in-depth troubleshooting steps to resolve the issue.

Step 1: Use a Private/Incognito Window

This is the most effective way to test if the problem is localized to your browser's existing cache and cookies.

1. Open a new InPrivate window in Edge (press Ctrl + Shift + N).
2. Navigate directly to https://portal.azure.com.

Attempt to sign in again.

If this works, it confirms the problem is with the data in your main browser profile. You can then proceed with the more aggressive cleaning steps below.

Step 2: Clear All Microsoft Sessions and Tokens

A simple cache clear doesn't always remove every token. Let's try to explicitly sign out of all Microsoft sessions.

1. Go to https://account.live.com and sign out of all sessions.
2. If you have access, also go to https://portal.office.com and sign out there as well.
3. In Edge, go to edge://settings/siteData.
4. Use the search bar to find Microsoft.
5. Click "Remove all shown" to clear all cookies and site data related to Microsoft domains.

Step 3: Disable Extensions and Check Date/Time

1. Go to edge://extensions and temporarily disable all extensions, especially any related to security or privacy.
2. Go to your PC's date and time settings and ensure that "Set time automatically" and "Set time zone automatically" are both turned on. Incorrect time can cause token validation failures.

Step 4: Check for Corrupt Browser Profile

If the issue only happens in Edge even after all these steps, your browser profile itself might be corrupted. You can create a new profile to test this.

1. In the top-right corner of Edge, click your profile picture.
2. Select "Add Profile".
3. Sign in with your Azure account and try accessing the portal again.

Official Documentation and References:

• Troubleshoot Azure subscription sign-in issues
• Clear Cookies and Site Data in Microsoft Edge

Let me know if this helps. Happy to assist further. Thank You!