This is an archive version of the document. To get the most up-to-date information, see the current version.

Adding On-Premises Microsoft SharePoint Organization

In this article

    To add a new on-premises Microsoft SharePoint organization, do the following:

    1. In the Select organization deployment type drop-down list, select On-premises.
    2. Select the Microsoft SharePoint Server checkbox.

    Adding Microsoft On-premises SharePoint Organization

    1. In the Server name and port field, specify a Microsoft SharePoint server name and the WinRM port.

    For the server name, you can use a DNS name of a server, NetBIOS name or its IP-address.

    1. In the Username and Password fields, specify authentication credentials to connect to the Microsoft SharePoint server using either of the following formats: domain\account or account@domain.

    For more information, see Required Permissions.

    Consider that using ADFS accounts to add on-premises Microsoft organizations is not possible. Only Office 365 organizations can be added with non-MFA enabled ADFS accounts.

    1. Select the Grant this account required roles and permissions checkbox to automatically add a user to the SharePoint Site Collection Administrators group and grant this user administrative privileges to access Microsoft SharePoint sites. This option also grants access to the User Profile service to work with OneDrive data.

    Adding Microsoft On-premises SharePoint Organization

    1. By default, Veeam establishes an SSL connection. To change this or skip one or more SSL verifications, click Advanced and select verifications to skip:
    • Skip certificate trusted authority verification
    • Skip certificate common name verification
    • Skip revocation check

    Adding On-Premises Microsoft SharePoint Organization 

    1. Wait for a connection to be established and click Finish.

    Adding Microsoft On-premises SharePoint Organization

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.