Saurabh_Bansal Thanks, that is EXACTLY the app I was using. I`ll go through this specific configuration guide and check again. But judging by the first glimpse that I had on that page, there is no explanation or additional guidance for why this is NOT working for me.
Again, the registration SEEMS to fail on the device NOT in Azure Universal print. Azure universal print "sees" the printer but the status says the printer is not accepting print jobs and I can`t get additional details from the printer.
And the printer immediately tells me that the registration fails when I open up said app after I got redirected to the on device web browser that is used to handle modern auth for the Azure tenant.
Sorry if this sounds a bit confusing. Short story is: I open the app on the Ricoh printer, I type in
Name: <printer name>
Tenant ID: <tenant id of our Azure tenant>
Client ID: <id of the oem printer registration app>
After that a 6 digit code is created and I get redirected to the Ricoh internal web browser and an Azure website opens up. I enter the 6-digit code plus MY PERSONAL global admin credentials. After that, the device is successfully registered IN AZURE! and the browser stays open (no additional redirect happening).
If I close said browser and/or open up the Universal print app on the Ricoh printer I get told, that the registration failed. After that the registration wizard starts from scratch asking for name, tenant id and client id.
We upgraded the printer and entire software on it YESTERDAY to the latest available version. But nothing changed.
So either this is a bug, or Ricoh needs something specific in the "OEM Printer Client Application" that I created (maybe additional API permissions?!) that aren`t documented anywhere (yet)?!
I really don`t know and it starts to really get annoying.