Adding organisation failing

[dmaunder]

I am trying to add an organisation on a new organisation on a fresh install of Windows 10 x64. I believe I have followed all the prerequisites.

When I run the Add Organisation wizard, it fails on the Connect to Power Shell line with the following error

[Window Title]
VEEAM BACKUP FOR MICROSOFT OFFICE 365

[Content]
Failed to execute cmdlet: Get-OrganizationConfig.
Please check permissions required for product operation (see Prerequisites section in the user guide).
The term 'Get-OrganizationConfig' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

[OK]

[Polina]

Hi Daryl,

Wich product version are you using? Are you adding an Office 365 organization or a hybrid deployment?
For an Office 365 org, please ensure your service account meets all the required permissions for Exchange, including the Organizations Configuration role.

[dmaunder]

Using Veeam Backup for Office 365 on an Office 365 tenant.

What is the exact powershell command to add the Organizations Configuration role?

[Polina]

You can assign this role either by using New-ManagementRoleAssignment cmdlet or by adding the required account to the Organization Management group via the Office 365 admin center.

Thanks!

[BrunoNovo]

My case ID is ID# 03697824

[arjenfurster]

I experience the same issue. Did you found a solution?

[Polina]

Hi Arjen and welcome to the Community!

If you're running VBO v3, please open a support call to get the fix. (kindly take a minute to post your case ID here)

Thanks!

[arjenfurster]

Hi Polina, I'm running VBO v4 and got this error.

I'm evaluating the software I'm not a customer yet. If it works as expected/required (since blob storage support it's on the projectlist again), I will onboard a 3000+ users customer. And as an MSP we will onboard a lot of more customers.

I've created support case 03893799

Error message: https://ibb.co/SQfkNtv

Because of MFA requirement we use Modern Auth.

[Polina]

Arjen,

Please make sure to grant all the required permissions to your service account as described here (for Exchange Online) and here (for SharePoint Online). This should help to resolve the problem.

Thanks!

[arjenfurster]

Indeed the solution was to not only add the Impersontation role to the Exchange Online Role Group where my Veeam serviceaccount was member of, but also the Role Management, Organization Configuration, View-Only Configuration, View-Only Recipients and Mailbox Search roles!

[deerninja]

I'm getting this same error with V.4. We are also evaluating the software. We do not have hosted Exchange but only SharePoint on O365. The issue that I am finding with the documentation and prerequisites is that there are a couple of permissions required for roles that do not exist, those roles seem to be available only if you have the Exchange hosting.

[Polina]

Hi deerninja and welcome to Veeam Forums!

If assigning granular permissions is not available, you can use the Global Administrator role.

[deerninja]

thank you, i will give that a go!

[deerninja]

ok, that got me through the Microsoft Graph connections. Now I'm facing the following error:
Connect to PowerShell: Connecting to remote server outlook.office365.com failed with the following error message: access is denied

any further ideas?

[Polina]

Are the legacy protocols allowed in your tenant? Kindly, take a look at this thread with a similar discussion.

[Jonathan]

Indeed the solution was to not only add the Impersontation role to the Exchange Online Role Group where my Veeam serviceaccount was member of, but also the Role Management, Organization Configuration, View-Only Configuration, View-Only Recipients and Mailbox Search roles!

Thanks Arjen, this worked for us as well!