Configure Microsoft 365 access
Before you start to configure Backup SLAs, Storware Backup & Recovery server has to get access to your Microsoft 365 organization configuration first.
Access to data is performed via an application configured in your Microsoft 365 organization.
Note: You can skip this step if you want to add your Microsoft 365 organization to Storware Backup & Recovery server using the Setup Assistant. If not, please proceed with the next steps.
Note: Storware Backup & Recovery does not store your Microsoft 365 administrative id and password.
Manually registering an application with Azure Active Directory
A new Microsoft 365 application has to be registered and configured in Azure Active Directory. When it's done, in the next step you can add the application (organization) to Storware Backup & Recovery server.
The instruction is as follow:
Go to the Azure portal (https://portal.azure.com/) page and sign in to your Microsoft account by using your Microsoft 365 administrative user ID and password.
In the home view, go to Manage Azure Active Directory (click the View button).
To open the Azure Active Directory admin center, in the left pane, click the ellipsis to expand the Show all menu, and then click Admin centers > Azure Active Directory.
In the tenant dashboard menu, click App registrations and then click New registration.
Specify a user-facing name for the Microsoft 365 application, on the Register an application page by entering a name in the Name field.
Use the default options for the remaining fields, and click Register. The app registration is set up with the user-facing name that you entered.
To obtain the application (client) ID, and directory (tenant) ID string, go to Azure Active Directory > tenant - App registrations > Owned applications. Click the application name, copy the application ID string and directory ID. These strings will be required later when you register the Microsoft 365 service on Storware Backup & Recovery server.
To create a client secret for this application ID, click Certificates & secrets > New client secret.
On the "Add a client secret" pane, enter any user name in the Description field, and click Add. A client secret is generated, and the value is then displayed in the Client secrets pane.
Copy the client secret to the clipboard by using the copy icon next to the Client secret value field. This character string is also used for registration with Storware Backup & Recovery server.
To add permissions for this application ID, click API permissions > Add permission.
Specify permissions for each API in the following table by taking the following actions. Select the API name, for example, Azure Active Directory Graph.
API Permission name Permission type Azure Active Directory Graph
Calendars.ReadWrite
Application
Microsoft Graph
Channel.Create
Application
Microsoft Graph
Channel.ReadBasic.All
Application
Microsoft Graph
ChannelMember.Read.All
Application
Microsoft Graph
ChannelMember.ReadWrite.All
Application
Microsoft Graph
ChannelMessage.Read.All
Application
Microsoft Graph
Chat.Create
Application
Microsoft Graph
Chat.Read.All
Application
Microsoft Graph
Chat.ReadBasic.All
Application
Microsoft Graph
Chat.ReadWrite.All
Application
Microsoft Graph
ChatMember.Read.All
Application
Microsoft Graph
ChatMember.ReadWrite.All
Application
Microsoft Graph
Contacts.ReadWrite
Application
Microsoft Graph
Directory.ReadWrite.All
Application
Microsoft Graph
Files.ReadWrite.All
Application
Microsoft Graph
Group.Create
Application
Microsoft Graph
Group.ReadWrite.All
Application
Microsoft Graph
GroupMember.Read.All
Application
Microsoft Graph
GroupMember.ReadWrite.All
Application
Microsoft Graph
Mail.ReadWrite
Application
Microsoft Graph
MailboxSettings.Read
Application
Microsoft Graph
MailboxSettings.ReadWrite
Application
Microsoft Graph
Member.Read.Hidden
Application
Microsoft Graph
Sites.FullControl.All
Application
Microsoft Graph
Sites.Manage.All
Application
Microsoft Graph
Sites.Read.All
Application
Microsoft Graph
Sites.ReadWrite.All
Application
Microsoft Graph
Team.Create
Application
Microsoft Graph
Team.ReadBasic.All
Application
Microsoft Graph
TeamMember.Read.All
Application
Microsoft Graph
TeamMember.ReadWrite.All
Application
Microsoft Graph
TeamMember.ReadWriteNonOwnerRole.All
Application
Microsoft Graph
TeamSettings.ReadWrite.All
Application
Microsoft Graph
TeamsTab.Create
Application
Microsoft Graph
TeamsTab.ReadWrite.All
Application
Microsoft Graph
TeamsTab.ReadWriteForChat.All
Application
Microsoft Graph
TeamsTab.ReadWriteForTeam.All
Application
Microsoft Graph
TeamsTab.ReadWriteForUser.All
Application
Microsoft Graph
User.Read.All
Application
Microsoft Graph
User.ReadWrite.All
Application
Office 365 Exchange Online
full_access_as_app
Application
SharePoint
Sites.FullControl.All
Application
SharePoint
Sites.Manage.All
Application
SharePoint
Sites.Read.All
Application
SharePoint
Sites.ReadWrite.All
Application
SharePoint
User.ReadWrite.All
Application
To set the permission "full_access_as_app" in the Office 365 Exchange Online API, click "Add a permission" option and in the "Request API permissions" window go to "APIs my organization uses" and search for "Office 365 Exchange Online", then select "Application permissions" and check "full_access_as_app" from "Other permissions".
To save the selected permissions, click Grant admin consent for <your organization name>.
Since you're granting tenant scoped permissions this granting can only be done via the appinv.aspx page on the tenant administration site. You can reach this site by typing the address: https://tenantName-admin.sharepoint.com/_layouts/15/appinv.aspx. (replace the tenantName with your tenant name). Once the page is loaded, do as follow:
Enter your App Id (client ID) and click the Lookup button.
Enter the App Domain name.
In the "App's Permission Request XML" window enter the following lines:
16. When you click on the Create button you'll be presented with a permission consent dialog. Press the Trust It button to grant the permissions.
17. Open Powershell command prompt and execute the command:
or download and install the module directly from this site
then
It enables the LegacyAuthProtocolsEnabled setting.
Last updated