UI Translation

Office 365

  1. We couldn't find your message inside the Office 365 service. However, it looks like our email protection service rejected ...
  2. We couldn't find your message inside the Office 365 service. However, it looks like our email protection service rejected ...
  3. We couldn't find your missing item based upon your search criteria. You may want to double check the email address of the ...
  4. We couldn't find your Office 365 mailbox. Please make sure that an Exchange Online license has been applied to your account. ...
  5. We couldn't find your on-premises Exchange servers. You can't set up a hybrid environment with this configuration. Click ...
  6. We couldn't get to identity services on the Web from your computer. TCP port 443 has to be open on your firewall for identity ...
  7. We couldn't get to Office 365 email from your on-premises environment. TCP port 443 has to be open on your firewall to connect ...
  8. We couldn't get to Office 365 from your on-premises environment using single sign-on. TCP ports 80 and 443 have to be open ...
  9. We couldn't obtain a security token in the response we received from your identity provider. {0} This isn't something you ...
  10. We couldn't reach some of the endpoints ('{0}'). Please check your network settings. See http://technet.microsoft.com/en-us/library/hh373144.aspx ...
  11. We couldn't remove the Active Sync partnership for user "{1}". You can manually remove the partnership by using the steps ...
  12. We couldn't remove the Active Sync partnership for user '{1}'.{0}You can manually remove the partnership by using the steps ...
  13. We couldn't resolve "{0}" from your machine and we could resolve it from cloud, please contact your administrator to resolve ...
  14. We couldn't resolve "{0}" from your machine and we could resolve it from cloud, Please contact your administrator to resolve ...
  15. We couldn't resolve Office 365 host name {0}, which is required for Outlook to connect to your account. Please try after ...
  16. We couldn't resolve one or more Office 365 host name on your computer. Contact your administrator for further assistance. ...
  17. We couldn't resolve {0} on your computer, but we could resolve it from the cloud. Contact your administrator to resolve your ...
  18. We couldn't restart Outlook. We need to restart Outlook in order to turn on tracing.{0}{0}Save any unsent items in Outlook, ...
  19. We couldn't restart Outlook. We need to restart Outlook so we can turn off tracing.{0}{0}Save any unsent items in Outlook, ...
  20. We couldn't restore this user. You don't have any available products to assign to this user. Go to Billing > Subscriptions ...
  21. We couldn't retrieve your mailbox properties at this moment. Please contact your Office 365 admin for further assistance. ...
  22. We couldn't validate the SSL certificate because the SSL negotiation was unsuccessful. This could have happened because of ...
  23. We couldn't verify domain '{0}': it already existed in an unverified or verified state when we tried to add it as verified. ...
  24. We couldn't verify domain '{0}': it no longer exists on your account when we tried to add it as verified. Please close the ...
  25. We couldn't verify your domain It usually takes a few minutes for your new records to propogate, but can take up to 72 hours. ...
  26. We couldn't verify your domain It usually takes a few minutes for your new records to propogate, but can take up to 72 hours. ...
  27. We couldn't verify your domain We didn't see any MX records when we checked. It usually takes a few minutes for your new ...
  28. We couldn't verify your nameserver records. We can usually find them in about a minute, but sometimes it can take several ...
  29. We couldn\'t add a member to the group. Please try again. Note that conference rooms and people outside your organization ...
  30. We couldn\'t add a member to the group. Please try again. Note that conference rooms can\'t be added as members of groups. ...
  31. We couldn\'t add members to the group. Please try again. Note that conference rooms and people outside your organization ...
  32. We couldn\'t add members to the group. Please try again. Note that conference rooms can\'t be added as members of groups. ...
  33. We couldn\'t connect to our payment servers.\u00a0 Some payment-related features may not be turned on in Bookings.\u00a0 ...
  34. We couldn\'t connect to the server for your other account. Please click the Back button and make sure that you entered your ...
  35. We couldn\'t determine your merchant account status. Some payments-related features may not be turned on in Bookings. Please ...
  36. We couldn\'t get all members of the distribution list or unified group to add them to the group because the list is too large. ...
  37. We couldn\'t open the image. It may have been moved or deleted. Please confirm that you can access the location where the ...
  38. We created logs of Outlook hang problems in this folder: {0} Please share the logs with your Office 365 admin or support ...
  39. We currently support upload of malicious and non-malicious attachments. E-mail and URL submissions will be supported soon. ...
  40. We detect that an email provider is already associated with {0}. If anyone is getting email with an address ending in @{0}, ...
  41. We detect you have a running batch, you can let us to clean up it for you or go to Exchange Admin Center to manually stop ...
  42. We detected a CNAME record for your domain: "{1}" points to "{2}".{0}This setting is not recommended and it will cause issues ...
  43. We detected a CNAME record for your domain: {1} points to {2}.{0}This setting is not recommended, and it will cause problems ...
  44. We detected a duplicate {selectedItem.PropertyNameLocalized} conflict on the value {selectedItem.PropertyValue} . All attribute ...
  45. We detected a few issues with some users in your company. The following is the list of issues, the users impacted and solutions. ...
  46. We detected a known crashing issue {0} times in your application event log. This issue is fixed in a recent update for {1}. ...
  47. We detected an %BRAND_OUTLOOK% crash on your computer and we know how you can fix it.{0}{0}Go to How to fix this crash , ...
  48. We detected an %BRAND_OUTLOOK% crash on your computer that you can fix by installing an Office update.{0}{0}For more information, ...
  49. We detected an %BRAND_OUTLOOK% crash on your computer that you can fix by installing an update. Before you can update %BRAND_OUTLOOK%, ...
  50. We detected an %BRAND_OUTLOOK% crash on your computer that you can fix by installing an update.{0}{0}Go to Install update ...
  51. We detected content in your org that contains W-2, 1040, 1054 or other tax-related info. Create a retention policy to help ...
  52. We detected that %BRAND_DYNAMICSCRMONLINE% for Outlook is not configured. We can try to fix this for you. Click Yes to run ...
  53. We detected that some of your users are using out-of-date versions of Outlook. Many features may not work on those versions. ...
  54. We detected that some of your users might not have a valid license to use email with Office 365. This can happen for any ...
  55. We detected that the %BRAND_DYNAMICSCRMONLINE% for Outlook add-in is disabled. We can try to fix this for you. Click Perform ...
  56. We detected that the %BRAND_DYNAMICSCRMONLINE% for Outlook is disabled. We can try to fix this for you. Click Yes to run ...
  57. We detected that you are using an out-of-date version of Outlook. Many features may not work on an old version. Actions: ...
  58. We detected that you haven't been assigned a license to use email with Office 365. Actions: Ask your administrator to go ...
  59. We did not detect a delay in the receiving of the message. Based on our records, Office 365 delivered your message in less ...
  60. We did not detect a delay in the sending of the message. Based on our records, Office 365 delivered your message in less ...
  61. We did not find any %BRAND_DYNAMICSCRMONLINE% instances for your tenant but verified you have a license. You may need to ...
  62. We did not get redirect response from {0}. {1}This is required for Outlook to get your Office 365 user settings (autodiscover). ...
  63. We did not get redirect response from {0}. {1}This is required for Outlook to get your Office 365 user settings (autodiscover).{1}Below ...
  64. We did not receive valid response from %BRAND_DYNAMICSCRMONLINE% endpoint {0}. If this problem persists, see {1} for more ...
  65. We did not receive valid response from Office 365 endpoint {0}. Please try again after some time. If this issue persists, ...
  66. We did not receive valid response from Office 365 endpoint. Please try again after some time. If this issue persists, contact ...
  67. We didn't find a configuration log file. Run the Microsoft Dynamics CRM Configuration Wizard. See {0} for more information. ...
  68. We didn't find any issues related to your %BRAND_DYNAMICSCRMONLINE% for Outlook configuration. You decided not to run our ...
  69. We didn't find any known crashes that we can fix for you. However, there are more troubleshooting steps you can do for %BRAND_OUTLOOK% ...
  70. We didn't find any problem with your %BRAND_DYNAMICSCRMONLINE% Web settings, and you decided not to run our recoveries at ...
  71. We didn't find any problem with your Outlook connectivity, and you decided not to run our Outlook recoveries at this time. ...
  72. We didn't find any problems with your Outlook account at the moment. To continue troubleshooting, download and run Microsoft ...
  73. We didn't find any problems with your shared calendar permissions. You have the following permissions to the shared calendar: ...
  74. We didn't find any shared mailboxes for your organization. Contact your %BRAND_OFFICE_365_SHORT% admin for help setting them ...
  75. We didn't get a response from the host {0} and the request timed out. Please try after sometime if this issue persists contact ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)