Du lette etter:

veeam office 365 the remote server returned an error: (401 unauthorized)

Issues authenticating - Veeam R&D Forums
https://forums.veeam.com › issues-...
EWS fails with HTTP status 401: Unauthorized and Microsoft Graph with Failed ... we use to administer O365 but that's only about 4 accounts, ...
KB4156: "The remote server returned an error: (403 ...
https://www.veeam.com/kb4156
07.05.2021 · Veeam Support Knowledge Base answer to: "The remote server returned an error: (403) Forbidden. Access denied" when performing Veeam Backup for Office 365 backup
How to resolve the unauthorized error 401 during Office ...
https://www.nucleustechnologies.com/blog/how-to-resolve-the...
29.12.2020 · The remote server returned an error: (401) Unauthorized. If you are facing this kind of error, then there may be multiple reasons behind this issue 1. The user ID is different than the UPN (User Principal Name). If the Office 365 account which you are using is different from the UPN from the Active Directory, then you will have to face the error.
The remote server returned an error: (401) Unauthorized
https://forums.veeam.com › public...
Veeam Community discussions and solutions for: Public folder backup ... returned an error: (401) Unauthorized of Veeam Backup for Office 365.
Upgraded repository now mailbox processing fails
https://forums.veeam.com › upgra...
Veeam Community discussions and solutions for: Upgraded repository ... with error: The remote server returned an error: (401) Unauthorized.
New sites and access rights - Veeam R&D Forums
https://forums.veeam.com › new-si...
Hi. We have som sites that I get the error - The remote server returned an error: (401) Unauthorized. Does SharePoint automatically give the ...
Public folder backup fails with: The remote server ...
https://forums.veeam.com/veeam-backup-for-office-365-f47/public-folder...
05.04.2017 · Veeam Community discussions and solutions for: Public folder backup fails with: The remote server returned an error: (401) Unauthorized of Veeam Backup for Office 365. Veeam R&D Forums. Technical discussions about Veeam products and related data center technologies. Skip ...
KB2714: “Unauthorized” error is ... - Veeam Software
https://www.veeam.com/kb2714
26.08.2018 · Backup jobs for SharePoint Online and/or OneDrive items fail with any of the following errors: 07-08-2018 11:11:39 3 (6640) Error: The request failed with HTTP status 401: Unauthorized. 07-08-2018 1
Sharepoint 365 Error Failed to process site (site) The remote ...
https://forums.veeam.com › sharep...
Veeam Community discussions and solutions for: Sharepoint 365 Error Failed to ... The remote server returned an error: (401) Unauthorized.
KB2714: “Unauthorized” error is thrown by SharePoint Online ...
https://www.veeam.com › ...
Product: Veeam Backup for Microsoft Office 365 ... 11:11:39 3 (6640) Error: The request failed with HTTP status 401: Unauthorized.
KB4169: Exchange backup fails after upgrading to Veeam ...
https://www.veeam.com › ...
After upgrading Veeam Backup for Microsoft Office 365 to v5, backup of Exchange Online data may fail with “Unauthorized (401)” error.
KB2969: Veeam Backup for Office 365 Complete Permissions
https://www.veeam.com/kb2969
26.06.2019 · 2969. Product: Veeam Backup for Microsoft Office 365 5.0, Veeam Backup for Microsoft Office 365 4.0. Published: 2019-06-26. Last Modified: 2021-08-12. Starting with Veeam Backup for Microsoft Office version 4c, two different modern authentication methods and a basic authentication method for working with Office 365 organizations are supported.
Office 365 Backup - Veeam R&D Forums
https://forums.veeam.com › office-...
"The request failed with HTTP status 401: Unauthorised" The account should have the required permissions, it passed the checkboxes and it ...
[SOLVED] Veeam Backup for 365 cannot enter Sharepoint ...
https://community.spiceworks.com/topic/2151461-veeam-backup-for-365...
27.07.2018 · Otherwise, support for SharePoint Online through Veeam Backup for Office 365 was just released, so there is not going to be many 'known' issues yet with resolutions. I suggest, posting this in the Veeam Forums or opening a case with Veeam Support as a next step