Office 365

  1. We do not currently support direct import of calendar files into %BRAND_OFFICE_365_SHORT% calendar or %BRAND_OUTLOOK_SHORT% ...
  2. We don't have contact information for the country or region you selected. To get help anytime, create an online service request. ...
  3. We don't have the details to show the organization chart for {0}. Organization details are provided by your admin or human ...
  4. We don't have the details to show your organization chart. Organization details are provided by your admin or human resources ...
  5. We don't want them to unsubscribe any more than you do, but allowing recipients to easily unsubscribe is required by law ...
  6. We don't, however, support the use of the Send-As, Receive-As, or Send on behalf of mailbox permissions in hybrid deployments ...
  7. We encountered a problem attempting to connect to the server. Verify the server name, or select the option to continue without ...
  8. We encountered unexpected response from the server. Can you wait for few minutes and retry? If problem continues, please ...
  9. We failed to get free busy information of this user, there is no message in server response. Please contact your Administrator ...
  10. We found a problem that may affect automatic configuration of Outlook. There are message class warnings on the Outlook AutoDiscover ...
  11. We found a problem that may affect automatic configuration of Outlook. There are message class warnings on the Outlook AutoDiscover ...
  12. We found a problem with your domain({0}) settings that causes failures while verifying your Office 365 account credentials. ...
  13. We found a problem with your Security Token Service ({0}) verifying your Office 365 account credentials. Your administrator ...
  14. We found a web proxy configured for you, sometime web proxy server becomes cause of high latencies and frequent disconnections ...
  15. We found all the expected authentication methods for your Office 365 account. Here are the authentication methods we found:: ...
  16. We found an error in the log file that indicates you may be encountering a known issue that can be caused by a Lookup field ...
  17. We found an error that indicates you may have duplicate subarea ids within your SiteMap customizations. Click on the link ...
  18. We found an error that may indicate that SQL CE is not installed or the installation is corrupt. Click on the link 'Help ...
  19. We found an error that may indicate that you have an old version of the Plugin Profiler solution installed which has a known ...
  20. We found an issue that's causing problems with Outlook. It looks like your domain isn't set up correctly. Actions: Ask your ...
  21. We found an issue that's causing problems with Outlook. It looks like your records aren't set up correctly for the following ...
  22. We found an issue. Passwords haven't sync recently to Office 365. Click on the link 'get help fixing this issue' in the actions ...
  23. We found an issue. Passwords haven't sync recently to Office 365. Details '{0}.' Click on the link 'get help fixing this ...
  24. We found an issue. You provided a sender and recipient that aren't part of your Office 365 organization. Please see your ...
  25. We found attributes on some of your Active Directory user accounts that have unsupported characters or are too long. You ...
  26. We found below Outlook autodiscover policies in registry: {0} {1} {0} {0} Please follow this {2} to disable these policies. ...
  27. We found issues with mailbox permissions. The setting known as AutoMapping may be affecting your Outlook experience. Click ...
  28. We found non-default server entries under the HKCU\Software\Microsoft\Office\{2}.0\Outlook\AutoDiscover\RedirectServers Windows ...
  29. We found non-default values under the HKCU\Software\Microsoft\Office\{2}.0\Outlook\AutoDiscover\RedirectServers Windows registry ...
  30. We found PreferLocalXML={0} as a policy setting in your Windows registry. This setting can cause problems with Office 365 ...
  31. We found public folders in your Outlook profile. You or your IT admin will need to migrate these folders to Office 365 if ...
  32. We found some message synchronization errors between Outlook and Office 365. You can see the errors by looking in the 'Sync ...
  33. We found some shared mailboxes you are associated with. Select the ones you want to troubleshoot. If your shared mailbox ...
  34. We found the '{0}' add-in on your computer. This add-in can cause Outlook to take a long time to close. You can disable the ...
  35. We found the '{0}' add-in on your personal profile. This add-in can cause Outlook to take a long time to close. You can disable ...
  36. We found the AVG antivirus add-in for Outlook installed on your computer. This can cause you to receive email messages that ...
  37. We found the Bluetooth add-in for Outlook installed on your computer. If you're having issues with Outlook, you should consider ...
  38. We found the Boot key in your Windows registry under HKCU\Software\Microsoft\Office\{2}.0\Outlook\AutoDiscover\. With this ...
  39. We found the FineReader add-in for Outlook installed on your computer. Older versions of this add-in can cause Outlook to ...
  40. We found the following %BRAND_ONENOTE% notebooks in your %BRAND_ONEDRIVE% folder. %BRAND_ONENOTE% notebooks have their own ...
  41. We found the following domains in your on-premises environment and added them to Office 365, and some of these domains still ...
  42. We found the following error in your CRMClientConfig.log file, which is related to your problem: {0}. See {1} for information ...
  43. We found the following Outlook Autodiscover policies in your registry: {0} {1} {0} {0}Use these instructions to disable the ...
  44. We found the iManage add-in for Outlook installed on your computer. This can cause Outlook to crash or stop working. If you're ...
  45. We found the PreferLocalXML value in your Windows registry. This value is used by Autodiscover, and it can cause problems ...
  46. We found the unsupported versions of Office installed on your machine, Though these versions can coexist with {0}, we recommend ...
  47. We found this add-in in the DoNotDisableAddinList entry in your Windows registry: {0}. This add-in was originally disabled ...
  48. We found unsupported characters in your Office 365 account sign-in name.{2} This isn't something you can fix yourself; contact ...
  49. We got the "Could not load file or assembly System.Data.SqlServerCe" error when we tried to configure %BRAND_DYNAMICSCRMONLINE% ...
  50. We got the generic error 0x80004005 from the referral service. This usually means that the server requires encryption. We're ...
  51. We got your request. We will contact you soon using the email address you gave us. When we are done, you can ask for more ...
  52. We had a problem checking your address book. The address book Bind operation returned this message: ecNotSupported. This ...
  53. We had trouble confirming your domain. Make sure you have logged in with the correct account on which the domain was registered, ...
  54. We had trouble confirming your domain. Make sure you have logged in with the correct account on which the domain was registered, ...
  55. We have a new {0} subscription, which replaces the {1} subscription that you've been using through the Office 365 Engineering ...
  56. We have a tool that can fix this problem Run Support and Recovery Assistant Ask the affected user to download the tool from ...
  57. We have been made aware that issues with Microsoft Dynamics Marketing Online Integration Services are in the process of being ...
  58. We have been made aware that network issues external to Microsoft are in the process of being resolved by service providers. ...
  59. We have been made aware that network issues external to Microsoft have been fixed and are being verified by service providers. ...
  60. We have changed the service infrastructure which will be included in this maintenance event. As a result of this change your ...
  61. We have completed steps to resolve the service incident. We anticipate that it will take an extended period of time for service ...
  62. We have confirmed that you own {0}, but we cannot add it to this tenant at this time. The domain is already added to a different ...
  63. We have confirmed that you own {0}, but we cannot add it to this tenant at this time. The domain was already added to a different ...
  64. We have detected that one or more staff members have a configuration error which will impact their availability on the booking ...
  65. We have found an error in the configuration log which indicates you have encountered a known issue that may prevent you from ...
  66. We have found device attached to your account on Office 365. Often, resetting the mobile partnership with Office 365 solves ...
  67. We have found device(s) attached to your account on Office 365. Often, resetting the mobile partnership with Office 365 solves ...
  68. We have implemented a fix and are in the process of validating the functionality that applies your Office 365 account changes ...
  69. We have implemented a fix and are in the process of validating the functionality that applies your Office 365 account changes ...
  70. We have implemented a fix for the issue of CRM Mobile being slow and unresponsive and are in the process of validating it. ...
  71. We have postponed the scheduled site upgrade date as per your request. We will notify you once we have a new date for you. ...
  72. We have received your order. It may take a few minutes to process. To see this order view this client's subscriptions. Be ...
  73. We have received your request and reserved your account. When your account becomes available, we will send an email message ...
  74. We have received your request to try out Office 365. Due to strong demand, we're reviewing all requests as they come in and ...
  75. We have successfully installed {0} on your machine. {1}Please open an Office application, sign in with your Microsoft account ...