Some time has passed, and with the latest release of Veeam for Office365, I was really hoping that the ability to pass credentials to a shared folder would be included in this version. Unfortunately, this isn't so.
We recently setup a new client on our Cloud Connect Server, with the following configuration:
w/ ---> Veeam Cloud Connect ---> Synology NAS Shared Folder ---> (cloud sync to) BackBlaze B2.
This configuration works FANTASTIC for backups; however it falls flat on its face for Office365.
Our cloud connect server is NOT domain joined to any of our domains; so has only local security to contend with.
Veeam for Office365 is installed on our Cloud-Connect VBR Server.
1. Connect to shared folder on NAS that is synchronized to B2 (unable to access due to inability to pass credentials)
2. Use local account on VBR server to run Veeam for Office365 services. Backups fail miserably, but can access the NAS.
3. Add computer account to NAS, run Veeam as LocalService. Unable to configure this, since the NAS or VBR server is not domain joined.
4. Enable Guest Account on NAS, and let everything run free. Security nightmare for audits.
5. Symbolic Link to NAS via local directory. Still need to pass credentials; can trick it with a persistent NET USE command, but will timeout after awhile.
I then created a case to only be told that Veeam for O365 needs to run as LocalSystem, which we already knew back on previous versions. I'm begging/pleading for development to add a credential field for shared folders, just like the rest of the Veeam Suite.
For now, we'll continue to backup Office365 for our clients with a product that rhymes with "A-slowness".
For this particular client, we installed backup for Office365 on their On-Prem server, backing up to a folder that gets backed up nightly with Veeam Windows Agent to our cloud connect server. This works, although in my opinion does not follow the "vision" that Veeam had for this product.