• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer

SuperTekBoy

Practical Help for Exchange & Office 365

  • Exchange
    • News
    • Tutorials
    • Solve a Problem
  • Office 365
    • News
    • Tutorials
    • Solve a Problem
  • Outlook
    • Tutorials
    • Solve a Problem
  • Books
  • Podcasts
  • Quick Links…
    • Generate or Renew SSL Certs for Exchange
    • Connect PowerShell to Exchange Online
    • Connect PowerShell to Office 365
    • Extend Schema for Exchange
    • Exchange Schema & Build Numbers
  • More…
    • Kemp Load Balancers
    • Other tech…
    • Videos
    • About SuperTekBoy
    • Contact Us

Office 365 Solutions

Office Activations fails ‘We are unable to connect right now.’

May 14, 2022 By Gareth Gudger 4 Comments

Share
Tweet
Share

When trying to activate (or sign in to) Microsoft Office with your Office 365 enterprise credentials, you may receive the following error. You may receive this error despite having internet access and being able to access other Office 365 resources.

Office Signin - We are unable to connect right now. Please check your network and try again later.
We are unable to connect right now. Please check your network and try again later.

Alternatively, you may receive this error.

Sorry, we are having some temporary server issues.

These errors are due to the Office suite (M365 Apps) believing it has no connection to the internet. The Office suite uses Windows to determine if it is connected to the internet. If Windows does not believe it is connected to the internet, you may see an exclamation symbol in your system tray over the network connection icon. Selecting the network connection icon may indicate that the connection has ‘Limited Access’ or ‘No Internet.’

Are the connection URLs blocked?

Despite this error showing in Office, this is a Windows problem. Several things could make Windows think it has “Limited Internet” or “No Internet.” Some culprits could include a misconfigured VPN, a web proxy intercepting or blocking traffic incorrectly, or restricted location awareness settings.

To determine if this is a VPN or web proxy issue, see if you can navigate to the following URL – http://www.msftconnecttest.com/connecttest.txt. Windows 10 attempts to connect to this URL, retrieve the TXT file, and confirm its content. You can plug this URL into your web browser to see if you can access that file. You should see a response stating “Microsoft Connection Test.”

Microsoft Connection Test URL accessed by Windows 10 Network Location Awareness service

If you don’t get this response, or you get an error accessing this page, make sure that any web proxies or firewalls do not block msftconnecttest.com (over port 80) in your environment.

If this test is successful, Windows 10 then attempts to resolve dns.msftncsi.com via DNS lookup. Note that this URL will not return any response in a browser. But you should confirm a firewall or web proxy does not block this URL.

For more information on what URLs Windows 10 uses to check network connectivity, plus registry keys to confirm the NCSI probe has not been disabled, check this article: An Internet Explorer or Edge window opens when your computer connects to a corporate network or a public network

[Read more…] about Office Activations fails ‘We are unable to connect right now.’

Filed Under: Office 365 Solutions, Outlook Solutions

Office Activation fails ‘This feature has been disabled by your administrator.’

March 17, 2022 By Gareth Gudger Leave a Comment

Share
Tweet
Share

When trying to activate (or sign in to) Microsoft Office with your Office 365 enterprise credentials, you may receive the following error.

Office Activation - This feature has been disabled by your administrator
This feature has been disabled by your administrator.

This error is likely a result of a group policy.

To check this, open Group Policy Management Console (GPMC). From the GPMC, expand your domain name (e.g., skaro.local) and Group Policy Objects.

Select your policy that is managing the Office suite and click the Settings tab. Expand User Configuration (Enabled) > Policies > Administrative Templates > Microsoft Office 2016 > Miscellaneous. If you see a setting named Block signing into Office that is Enabled, this is the culprit.

Group Policy - Block signing into Office Group Policy Management Console

Note: If you do not see this setting, I recommend checking all group policies currently applied to the impacted user. You can get this by running GPRESULT from a command prompt on your impacted user’s computer.

[Read more…] about Office Activation fails ‘This feature has been disabled by your administrator.’

Filed Under: Office 365 Solutions, Outlook Solutions

RPC/HTTP & Security Defaults may prevent Outlook reconfiguration after migrating to Exchange Online

March 14, 2022 By Gareth Gudger 2 Comments

Share
Tweet
Share

In a previous article, we discussed how a conditional access policy blocking basic authentication prevents Outlook clients (leveraging RPC over HTTP) from reconfiguring after a mailbox migration to Exchange Online. This is due to RPC over HTTP not supporting modern authentication. On the other hand, Outlook clients leveraging MAPI over HTTP would reconfigure without incident. This is due to MAPI over HTTP supporting modern (and basic) authentication.

This article explores how security defaults, which Microsoft has been enabling on all new tenants to block basic auth, could also prevent Outlook clients (leveraging RPC over HTTP) from reconfiguring after migration to Exchange Online.

How to check if Security Defaults are enabled (modern authentication is enforced)

To determine if security defaults are enabled in your tenant.

Log into the Microsoft 365 Admin Center. From the left pane expand Settings and select Org Settings. From the Services tab, select Modern Authentication. The Modern Authentication pop-out will identify if security defaults have been enabled.

The screenshot below shows the message that security defaults are enabled, indicating that modern authentication is required and basic auth connections are blocked.

M365 Security Defaults Enabled

If security defaults have not been enabled in your tenant, the modern authentication pop-out will have configurable options. The screenshot below shows that modern authentication has been enabled (but it is not enforced). We can also see which protocols permit clients to use basic auth. Based on the selections in the screenshots, Outlook clients are still permitted to use basic auth (via either RPC over HTTP or MAPI over HTTP).

M365 Security Defaults Disabled

Tip: While not the focus of this article, I highly recommend working towards disabling basic auth on as many protocols as you can before the October 1st, 2022 deadline. This not only improves your security posture prior to October but also gets you prepared for the retiring of basic auth.

[Read more…] about RPC/HTTP & Security Defaults may prevent Outlook reconfiguration after migrating to Exchange Online

Filed Under: Exchange Solutions, Office 365 Solutions

Outlook 2013: Your account is in a bad state

November 19, 2021 By Gareth Gudger Leave a Comment

Share
Tweet
Share

Starting November 1st, 2021, only Outlook 2013 SP1 (build 15.0.4971.1 and greater) will be able to connect to Microsoft 365 services. This means older Outlook 2013 builds, and Outlook 2010 and earlier will not connect to Microsoft 365. This new requirement goes hand in hand with the deprecation of basic auth, requiring Outlook 2013 SP1 (build 15.0.4753.1 and greater). Microsoft is deprecating basic auth on October 1st, 2022.

That said, if you are already blocking legacy auth for Outlook clients (or you are reading this post after October 1st, 2022), you may receive the following error when trying to sign in to your Office 365 account with Outlook 2013 or any other Office suite product. In addition, your Outlook 2013 client might not be able to connect to your Office 365 mailbox either.

When signing in to your Office 365 account via File > Office Account > Sign In from any Office suite product, you receive the following error.

Your account is in a bad state. Please sign-in to this account online to address the issue.
Your account is in a bad state. Please sign-in to this account online to address the issue

Alternatively, you may first see the error below which can then lead to the error above when you click the Fix me button.

Account Error: There are problems with your account. To fix them, please sign in again.
There are problems with your account. To fix them, please sign in again.
[Read more…] about Outlook 2013: Your account is in a bad state

Filed Under: Office 365 Solutions, Outlook Solutions

Exchange Online PowerShell fails to connect with error AADSTS50011

November 16, 2021 By Gareth Gudger Leave a Comment

Share
Tweet
Share

If you receive the following error when trying to connect to Exchange Online via PowerShell, then you will need to upgrade the Connect-ExchangeOnline PowerShell module.

AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application
Exchange Online PowerShell fails to connect error AADSTS50011

Resolving AADSTS50011 for Connect-ExchangeOnline

To resolve, launch PowerShell and run the following command. If you do not trust the PowerShell gallery you may also be prompted to confirm the installation from an untrusted gallery. Press “Y” to confirm.

 C:\> Update-Module ExchangeOnlineManagement

You are installing the module from an untrusted repository. If you trust 
this repository, change its InstallationPolicy value by running the 
Set-PSRepository cmdlet. Are you sure you want to install the module 
from 'PSGallery'?
[Y] Yes  [A] Yes to All  [N] No to All  [S] Suspend  [?] Help: Y

At this point, it is best to close and reopen any PowerShell windows you had open and reissue the command Connect-ExchangeOnline. The issue should now be resolved.

[Read more…] about Exchange Online PowerShell fails to connect with error AADSTS50011

Filed Under: Exchange Solutions, Office 365 Solutions

Workaround: Replying to a message with an invalid S/MIME digital signature fails

July 22, 2021 By Gareth Gudger 6 Comments

Share
Tweet
Share

If you received a message with an invalid or untrusted S/MIME digital signature, you might have problems replying to that message with Outlook on the Web (OWA).

The inability to reply is not necessarily a bad thing as it might indicate an impersonation attempt. Impersonation is where a bad actor pretends to be someone you know, often for financial gain. A common example of impersonation is a bad actor pretending to be a CEO asking their company accountant to wire money to the bad actor’s bank account.

So, if you see a failed digital signature, it is a good time to pause and determine if the sender really is who they say they are through other verified mechanisms (e.g., call them on a trusted phone number). Then validate if they are aware of the digital signature issue to see if they are already working to resolve it.

If using a product like Office 365, you can also check if the message has failed any impersonation checks. For example, are safety tips in OWA warning that you don’t typically receive mail from this sender with that email address.

The screenshot below provides an example of a message received in OWA where the S/MIME digital signature is not considered valid or trusted. Clicking the click here link gives us some additional insight into the error. We can see OWA does not trust this certificate because it has a broken certificate chain, more than likely caused by a missing or expired intermediary cert.

The digital signature on this message isn't valid or trusted OWA

When attempting to reply to this message in OWA, you may receive the following error.

This message can't be sent right now. Please try again later.
This message can't be sent right now. Please try again later.
[Read more…] about Workaround: Replying to a message with an invalid S/MIME digital signature fails

Filed Under: Exchange Solutions, Office 365 Solutions, Outlook Solutions

  • Page 1
  • Page 2
  • Page 3
  • Interim pages omitted …
  • Page 5
  • Go to Next Page »

Primary Sidebar

Want to stay up to date?

Sidebar Form

Join thousands of IT professionals and get the latest Exchange & Office 365 tips and tutorials direct to your inbox

DigiCert Banner 300x348

(help support us using our affiliate link)

Footer

Site Navigation

  • Subscribe to blog
  • About SuperTekBoy
  • Disclaimer
  • Privacy & Cookies
  • Contact Us

Want to stay up to date?

Footer Form

Join thousands of IT professionals and get the latest Exchange & Office 365 tips and tutorials direct to your inbox

Join the conversation

  • Twitter
  • LinkedIn
  • Facebook
  • YouTube
  • RSS

Copyright © 2025 · SuperTekBoy LLC