Office 365 Now Flagging Some AuthnRequests Forced?

[Klingenstein, Nate]

This is apparently related to a specific client and there will be a patch issued in the future.  Do as you will until then...

________________________________
From: users <users-bounces at shibboleth.net> on behalf of Klingenstein, Nate <nklingenstein at calstate.edu>
Sent: Tuesday, October 10, 2017 12:47:04 PM
To: Shib Users
Subject: Office 365 Now Flagging Some AuthnRequests Forced?

Either these just started showing up today at high noon, or I never noticed this flag being set before.

<samlp:AuthnRequest ForceAuthn="true"
    ID="_a186afb7-e2c0-4307-96b2-5de7df8b5fe1"
    IssueInstant="2017-10-10T18:56:41.728Z" Version="2.0" xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
    <Issuer xmlns="urn:oasis:names:tc:SAML:2.0:assertion">urn:federation:MicrosoftOnline</Issuer>
    <samlp:NameIDPolicy Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"/>
</samlp:AuthnRequest>

Count 28 so far.  Enabled forced as a workaround for now.  Anyone else see this?  Was this normal?  Am I nuts?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20171010/12fd769b/attachment.html>