Universal Print: When is a http 403 error not a http 403 error?

TL;DR Because its not due to lack or rights but lack of a license and license allocation via AD Groups is not instant

Interesting one this one a client has some of our Correspondence Management Software installed and have just started using Universal Print but every time they sent a print job off they got back a http 403 error, which implies they lack rights.

The msgraph call that caused the error was:

/print/queues

We checked and the Azure Active Directory Application Registration had been granted

Then I thought what is the application and the user have the rights to access the print queue but the user doesn’t have a Universal Print license what response will you get. I couldn’t find the explicit answer to that anywhere. So I asked the client ‘does the user have a Universal Print license’. They said no he doesn’t.

They quickly allocated the user to a group that allocates a UP license and we retested. Still nothing.

Then I remembered the fun and hi-jinks we had had at another client who used AD groups to allocate licenses. So we went to lunch. An hour later we got retested and lo and behold the user was able to place jobs on the print queue from our software.

TL;CR Because its not due to lack or rights but lack of a license and license allocation via AD Groups is not instant