When an admin configures Autopilot for an organization CloudExtend begins 'watching' for emails that are set for Autopilot by licensed users. In the event the watch is unsuccessful CloudExtend will send the end user an in-app message (1 time only) advising them that there was an issue enabling the Autopilot watch.

Possible reasons for Autopilot watch failure

  • The user's User Principal Name (UPN) must be the same as their email address.
    This UPN can be confirmed by your Microsoft 365 Admin in the Microsoft 365 Admin center under the Username column as seen below.
  • The user's Outlook email address must be identical to their NetSuite login and it must be a Microsoft 365 account (for example, if you're using a Gmail account to login to NetSuite which is, of course, different than your Outlook email, the watch will fail).
  • Your admin did not grant access to the email domain you are using during the configuration stage when enabling Autopilot. The admin can regrant consent and should be sure that when grating consent they are logged in with the same domain as the user (or a properly configured alias associated with the domain)
    For example, if the user's email is jane@abc.com the admin should also be logging in with the same domain, ie admin@abc.com.
Did this answer your question?