Sway Sign-in button doesn't respond

Dear IanDOE_21,

Thank you for querying the Microsoft Community forum.

Based on your description, you encountered an error when signing into Sway. Even on different devices and via different networks as well, you still can’t sign in and this is accompanied by an error message.

I understand your frustration and apologies for the inconvenience.

I tried signing in to Sway and I had no issues. Also, there’s no incident associated with Sway in the Microsoft Service Health dashboard.

You mentioned "I tired to press Sign-in on multiple devices", may I confirm whether you have tried different browsers? If not, I would suggest that you switch to different browsers. The issue maybe be specific to the browser you are using and some security policies may differ across browsers.

Feel free to reach out incase you still face issues with signing-in to Sway with more information as seen below. I’d be happy to help.

• Does this issue affect others under the same Microsoft tenant as you? This will inform me on whether it is an issue specific to your account or your tenant.

Thank you for your understanding and patience.

Sincerely,

Sophia

Hi Sophia,

I tried logging in on a windows computer with:

• Chrome - issue screenshot that I originally posted
• Firefox - screenshot attached here.

I also tried via a mobile network on iOS.

I tried with Safari, Chrome and Edge. The sign in button didn't respond in all cases. I can't provide a screenshot because it wouldn't be very illustrative.

Dear IanDOE_21,

Thank you for reaching out once again.

Having tried signing-in with different browsers you still face the same issue.

Keep in mind that the error message you're receiving (related to the X-frame) suggests that there may have been too many repeated sign-in attempts that has probably led to Microsoft’s login page being blocked from loading inside a frame due to security settings. I would suggest that you retry after a 24H wait to see if this persists.

Furthermore, I would suggest that you try accessing Sway in incognito mode on your browser. To do so, open a new browser window > click on the three dots at the top right corner > login to https://portal.office.com and enter your Office 365 account details > click on the 9 dots at the top right > search and click on the Sway. This will completely take out browser related issues.

In case you are using a VPN or proxy, turn them off and try to sign in again since some network configurations may block authentication pages.

As previously asked, could you let me know if this issue affects others under the same Microsoft tenant as you? This will inform me on whether it is an issue specific to your account or your tenant.

Also, does this issue occur with other Microsoft 365 apps as well? Try signing-in to any other web app (e.g. Word online) and see if you encounter the same issue which will permit me determine if it is an issue with just Sway or the Microsoft suites.

If possible, try contacting the IT admin of your organization to check if Sway might have been disabled at the organizational level - How to find the organization’s administrator. The admin can check if Azure Active Directory (AAD) Conditional Access Policies to ensure that no policy is preventing access to Sway. For more information on conditional access, this link can be checked.

Thank you for your patience and understanding.

Sincerely,

I had also run into similar issue. Also seeing that the same "Refused to display 'https:.....' in a frame because it set 'X-Frame-Options' to 'DENY'. "

I had try it again after 24 hours, still got the same result.

Tried Safari and Chrome on Mac, no luck.

If I click on the Sway logo on the upper left hand side, I am able to sign in. However, that's a pain for general user of my organisation.

We are experiencing the same issue. We use Sway to send out our weekly school newsletter. It is set to not require a sign-in to view, yet it asks for one and the Sway login page is unresponsive as described by the original poster.

We have been doing this weekly for the last five years. The last two weeks are the only time we have run into this issue.