VBO Application creation in Azure

[disk91]

Hello, I'm trying to execute the Application registration in Azure through the API, I've found a previous forum post and nielsengelen sample code but it seems to be outdated with API evolution.

I would like to verify the userCode validation by the user and took a look to the MS API - https://login.microsoftonline.com/<tena ... uth2/token

This api is requiring clientId:

client_id Required The Application (client) ID that the Azure portal – App registrations experience assigned to your app.

But client ID is passed by VBO when creating the userCode but not returned as a result for the userCode creation. So apparently we are not able to do this check.

What is the current way to correctly create an Organization against this now ?

[nielsengelen]

Hi Paul, the logic is still the same (since I have it in my web-based unofficial portal ). The example (https://github.com/nielsengelen/veeam-r ... MFA-Tenant) is still working here.

Additionally, I've made 2 blogs about this:
Veeam Backup for Microsoft Office 365 RESTful API: Adding MFA-enabled Organizations: https://foonet.be/2020/09/24/veeam-back ... nizations/
Veeam Backup for Microsoft Office 365 RESTful API: Authentication against MFA-enabled Organizations: https://foonet.be/2020/09/28/veeam-back ... nizations/

If you are doing the authentication, you get the userCode and all the rest directly from the MS API - not VBO. The only part where this is required is when you do the actual restore.

Can you clarify in which part you are struggling (or which API call)? If you have some more insight on the setup, I could do some tests.

[disk91]

I made it working without having to do this but it would be great to verify if the en user did validate the user code or not. For querying the Azure API we need to provide a client ID, not the Azure user-code. this client ID is only know by the VBO if I correctly understood the API in v5. So it can't be made from a custom application piloting VBO with the API.
It's not blocking anymore but it would be good to add. Let me know if you have some exemple.
I've taken a look to some of your repos nielsegelen, they are really helpful. But what I show seemed to be using a previous version of VBO api where the API call seemed to be a bit different. That was some ays ago, I could be wronf as focus now on different part.
Paul

[nielsengelen]

Hi Paul, there are no changes on this logic between v4c and v5.

The whole flow is also described in the user guide. I think with client ID, you mean the application ID (the random numbers?) - those can be found in the Azure portal as well.

On polling for verification for the restore, this is indeed something which is not possible for now. Polling is only possible while waiting for the authentication against VBO.