New Veeam365 enterprise apps aren't created with the updated permissions for v8

[pat_ren]

Hi all,

As per https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80

We have had to update permissions on a lot of our orgs since upgrading to v8. I created a new enterprise app for a new tenant to test if this also needed updating and it appears to be missing some permissions from the KB.
The following are missing in a new application.

Microsoft Graph (application permissions):
ChannelMessage.Read.All
ChannelMember.Read.All

Am I incorrect in assuming that a freshly deployed App should have all of the required API permissions granted to it?

[pat_ren]

Any confirmation on if this is a bug or working as intended?

ChannelMember.Read.All specifically is a required permission for teams backups.

[Mike Resseler]

Just to be clear, even if you add a new tenant, the right permissions are not added? If so, then it is indeed a bug. During an upgrade, we can't force the new permissions so you would need to reauthorize and then consent to the new permissions, but a new tenant added should get those from the first run. Let me know so I can work with QA on it if needed

Thanks @pr_osit

[pat_ren]

Hi Mike, sorry can't reply directly to your reply or @ you so hopefully you see this.
This is a new tenant, not an upgrade of an existing tenant. I have tested creating some new orgs after upgrading to V8 and noticed the permissions mentioned are missing which I believe should be included in a newly created app registration.
I'm on v8.0.2.200 if it matters.

Cheers

[Mike Resseler]

It matters indeed. I will get to QA and talk to them to see if this is an oversight

[Mike Resseler]

@pr_osit
Just a quick question... Did you check the "Team Chats" backup when adding the organization? If you haven't, that might have been the reason why you are missing it, since (if I am not mistaken) those permissions are needed for that.
Second question: Did you see errors while trying to backup teams?

[pat_ren]

Hi Mike,

Good question, I did not enable teams chat for this org so that may indeed be why the permissions were not assigned when it was created. I'm not currently backing up teams chats for that client so there's no errors, but we may be enabling it in the future. I hadn't thought about that. I am guessing if we were to tick that option within the org, upon completing the edit organisation, it should re-configure itself with the correct permissions.

I was thinking the app would just grant all permissions required when being first configured, but this might be working as intended then. Thanks for your clarification.