Please guide us , how can we regenerate that

Hi, I'm Descope's AI assistant. I need more context to help you regenerate something. Could you clarify: • What specifically are you trying to regenerate? (API key, token, certificate, etc.) • Where in the Descope console or which integration are you working with? Once I understand what you're looking to regenerate, I can provide the exact steps.

We are using Microsoft Social Login

Got it — you're trying to regenerate Microsoft OAuth credentials for your social login, right? Regenerate Microsoft OAuth Credentials For Microsoft social login, you need to regenerate the client secret in your Microsoft Azure application. In Microsoft Azure Portal 1. Navigate to Azure Active Directory → App registrations 2. Select your application 3. Go to "Certificates & secrets" 4. Under "Client secrets", click "New client secret"

Description: Descope Integration
Expires: Choose your preferred expiration (6 months, 12 months, or 24 months)

5. Copy the new secret value immediately (it won't be shown again) Update Descope Configuration 1. Go to Descope Console → Settings → Authentication Methods → Social Login 2. Find your Microsoft OAuth provider 3. Click "Use my own account" 4. Replace the Client Secret with your new value from Azure 5. Save the configuration • The old client secret will stop working once you save the new one • Test your authentication flow after updating to ensure it works properly Custom Social Login with Microsoft | Descope Documentation

Authentication Account is from Descope

Descope-Managed Microsoft OAuth If you're using Descope's default Microsoft OAuth (not your own Azure app), you can't regenerate the secret yourself. Check Your Configuration 1. Go to Descope Console → Settings → Authentication Methods → Social Login 2. Look at your Microsoft provider settings 3. If you see "Use Descope's account" selected, this is managed by Descope Contact Descope Support Since this is a Descope-managed authentication account: 1. The secret expiration should be handled automatically by Descope 2. If users can't login, this may indicate a service issue 3. Contact Descope support immediately with: - Your project ID - Error messages users are seeing - When the issue started Temporary Workaround Consider switching to your own Microsoft Azure app: 1. Create your own Azure AD application 2. Configure it with Descope following the custom setup guide 3. This gives you full control over credential rotation • Descope-managed OAuth providers should handle credential renewal automatically • If they're failing, this requires Descope engineering intervention

Our Project Id is P2Vsv0sfXLReuXSrMtIs0FiygtD1

Escalate to Descope Support With your Project ID

P2Vsv0sfXLReuXSrMtIs0FiygtD1

, you need immediate support assistance since this is a Descope-managed Microsoft OAuth account. Contact Descope Support Now 1. Email support with: - Project ID:

P2Vsv0sfXLReuXSrMtIs0FiygtD1

- Issue: Microsoft social login failing, suspected expired secret - Impact: Users cannot authenticate - When it started failing 2. Or use the support chat in your Descope Console Immediate Action Items While waiting for support: 1. Check if other authentication methods work (email, password, etc.) 2. Temporarily disable Microsoft login if you have alternatives 3. Communicate with affected users about the temporary issue Expected Resolution Descope engineering will need to: • Verify the OAuth credential status • Rotate the expired secret on their managed application • Restore service (usually within hours) This is a service-level issue that requires Descope's direct intervention since you're using their managed Microsoft OAuth provider.

“error_message”: “[E062209] Token exchange with OAuth provider failed, please validate your OAuth setup: Failed to exchange OAuth base token [error: oauth2: \“invalid_client\” \“AADSTS7000222: The provided client secret keys for app ‘6a6efabd-078f-46f6-8a3c-98ca107af948’ are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: 8e4593fd-639f-45c2-ab0c-63271a830a00 Correlation ID: 6454134b-6ee8-4ef2-9d68-9265b0bd504f Timestamp: 2026-03-16 133244Z\” \“https://login.microsoftonline.com/error?code=7000222\“]”

Confirmed: Microsoft OAuth Secret Expired The error confirms your Microsoft OAuth client secret has expired. The Azure app ID

6a6efabd-078f-46f6-8a3c-98ca107af948

needs new credentials. Since This is Descope-Managed You cannot fix this yourself - Descope must update their managed Microsoft application. Immediate Action Required Contact Descope support with this exact error:

Project ID: P2Vsv0sfXLReuXSrMtIs0FiygtD1
Azure App ID: 6a6efabd-078f-46f6-8a3c-98ca107af948
Error: AADSTS7000222 - Client secret expired
Trace ID: 8e4593fd-639f-45c2-ab0c-63271a830a00

Expected Resolution Descope engineering will: 1. Access their Azure portal for app

6a6efabd-078f-46f6-8a3c-98ca107af948

2. Generate new client secret 3. Update their OAuth configuration 4. Restore Microsoft login functionality Timeline This should be resolved within hours once Descope support receives your ticket. The error message provides them everything needed to identify and fix the expired credentials.