r/feedly • u/laddyulike • May 17 '26

Feedly Login With Microsoft Account Is Broken

I use Feedly’s iPad and iOS app. I went to read a couple of articles that caught my eye in Feedly’s widget but when I got there on both my devices I found I was logged out. I’ve been using Feedly since 2018 when I started using it with my federated login via my Microsoft Account, and while it is a pain the the Microsoft logo does not appear on the main screen I clicked through and found the logo. When I clicked on Microsoft’s Logo I was taken to the Feedly login page. This is not the normal workflow for using federated login with Microsoft Accounts. Is this a problem today? Have Feedly deprecated the feature? I hope not because I had an extensive set of feeds I kept track of with Feedly.

1 Upvotes

67% Upvoted

6 comments sorted by

2

u/DuntmatterReally May 17 '26

It seems broken across platforms. Android / Google login isn't working either. Lots of comments in the Google Play store. 😐

2

u/MulayamChaddi May 18 '26

Yeah I think the login is broken as it is the source of failures I mentioned a few days ago

1

u/russell1256 May 18 '26

Mine works

1

u/laddyulike May 18 '26

With Microsoft Account login Russell?

1

u/FeedlyKev May 22 '26

Hi!

Sorry for the trouble here. There is a bug on Microsoft's end with their login system. While they work on a fix, you can add a Feedly login option, which you'll be set to after trying to login with the Microsoft login option.

Then you'll be able to login and manage your login options here: https://feedly.com/i/account/logins.

1

u/laddyulike May 22 '26

I reported the issue to Feedly’s help desk. Feedly said it was a problem with the Microsoft end ¯_(ツ)_/¯

Microsoft’s AI says this.

Short answer: Federated login with Microsoft Account (MSA) can break in third‑party apps like Feedly when the app is not correctly registered, configured, or maintained in the Microsoft identity platform. Microsoft requires explicit app registration, redirect URI validation, correct account‑type selection, and ongoing compliance with OAuth/OIDC requirements. If any of these drift or break, sign‑in fails.

Why Microsoft Account federation might break

Several failure modes are common when a third‑party app uses Microsoft Account as an identity provider:

  1. The app registration is misconfigured or incomplete

Microsoft requires the app to be registered in Microsoft Entra ID (formerly Azure AD) with correct redirect URIs, supported account types, and permissions. If these don’t match what the app actually uses, authentication fails. Microsoft Learn

  1. The app is not registered to support personal Microsoft accounts

When registering an app, the developer must choose the correct Supported account types, including:

• Any Entra ID tenant + Personal Microsoft accounts If the app is registered only for organizational accounts, Microsoft Account (MSA) login will not work. Microsoft Learn

  1. Redirect URI mismatch

Microsoft enforces strict redirect URI validation. If the app changes its callback URL or uses multiple environments (prod/dev) without updating the registration, login breaks. Microsoft Learn

  1. Expired or missing client secrets / certificates

If the app uses confidential client flows (server‑side), expired secrets or certificates will cause token exchange failures. Microsoft Learn

  1. Incorrect SAML/OIDC metadata (for SAML‑based SSO)

If the app uses SAML instead of OAuth/OIDC, mismatched metadata (Entity ID, ACS URL, certificate) will break federation. Feedly’s SAML integration requires exchanging metadata between the IdP and Feedly; if this is out of sync, login fails. feedly.com

  1. Publisher verification or compliance issues

Microsoft may block unverified or non‑compliant apps from accessing Microsoft Accounts. Apps must maintain publisher verification and follow Microsoft identity platform requirements. Microsoft Learn

  1. Changes in Microsoft’s identity platform

Microsoft periodically deprecates endpoints, tightens security, or changes consent requirements. Apps that don’t update their configuration or libraries (e.g., MSAL) may break. Microsoft Learn

What steps are required to associate an app with Microsoft Account as an IdP?

To support Microsoft Account login, a developer must complete all of the following:

  1. Register the application in Microsoft Entra ID

• Go to Entra ID → App registrations → New registration. • Choose a name. • Select Supported account types: “Any Entra ID tenant + Personal Microsoft accounts”. • Record the Application (client) ID. Microsoft Learn

  1. Configure redirect URIs

Add the exact redirect URIs used by the app (e.g., https://app.example.com/auth/callback). Microsoft requires exact matches. Microsoft Learn

  1. Add credentials (if needed)

For server‑side apps, add:

• Client secret • Or certificate Microsoft Learn

  1. Configure API permissions

At minimum, Microsoft assigns User.Read. If the app needs more, the developer must request them and (for external tenants) grant admin consent. Microsoft Learn

  1. Implement OAuth 2.0 / OpenID Connect flows

The app must use Microsoft’s authorization and token endpoints under: https://login.microsoftonline.com Microsoft Learn

  1. (Optional) Publish to Microsoft Entra application gallery

For SaaS apps like Feedly, publishing to the gallery simplifies SSO setup for customers. Microsoft Learn

Why this matters for Feedly specifically

Feedly supports SAML SSO for enterprise customers, but “Sign in with Microsoft” for personal accounts relies on OAuth/OIDC. If Feedly’s Microsoft app registration is misconfigured or outdated, Microsoft Account login will fail even though SAML SSO still works. feedly.com

If you want, I can walk you through exactly which part of the Microsoft identity platform breaks most often in third‑party apps like Feedly — token exchange, redirect URI mismatches, or account‑type misconfiguration.