might be unrelated but did you use the "all users" button in intune when setting up the device compliance ?

if yes, you need to use a specific group otherwise it won't work as per doc

Also....

In my case, our macs appear under the device section in user's account, not in the Devices > macos section

Not very user friendly....

Hi, thx for answering.

@jpoirson We have a specific group configured. :)

Jamf support just answered friday, that here is some problem with the jamf framework on the mac's.

sudo jamf manage before starting the registration process with company portal helps in most cases,

Seeing this is exact same behavior. We just set this all up yesterday for our limited test group and the test Macs yesterday enrolled fine, the jamfAAD app popped up as expected.

Today, adding a few more devices for the same limited users, all 3 new devices behaved as described above and we see the same "No Azure Tenant Set up" log entry.

Running `sudo jamf manage` and then flushing the Intune Registration policy in Jamf allowed the registration to complete as normal again.

One note:

So far, if Microsoft Edge is the default browser, the browser call to the Company Portal by jamfAAD to select the certificate and add it to Keychain fails and the user is prompted every time to install Company Portal.

Changing the default browser to Google Chrome or Safari work as expected.

The exact same thing happened to me.  I've been pulling my hair out over this for the past few weeks trying to figure out where I went wrong in the configuration.  Also opened a technical support ticket last week.  The rep said he would look into it.  Still waiting for a reply.  Good thing I found this thread.  The sudo jamf manage and flushing the policy worked.  Both my test machines now have a green tick mark beside them on Azure and are listed as compliant once again.

I wasn't getting the second prompt during the registration process (It did initially and then it stopped appearing, even if I deleted the computer record from Azure and erase/installed the Mac).  The above fixed it.  Many thanks to all! :)

@mt-nw  Have you tried using the WKWebView to negate the need for a web browser during registration.

Apply it to com.jamf.management.jamfAAD

I am now in contact with jamf support and have sent a lot of logs from different tests.

My experience actually is:

Different browsers -> different expereince

clean installed macbooks and fresh enrolled with prestage -> only safari browser installed, and after "sudo jamf manage" -> the sing in to azure through the self service must be done twice. The first try stopps on the login through browser after company portal has registered the device. So jamfaad do not start correct. The second time it works. 

We did end up deploying that thanks to your suggestion and finding it in the Jamf Troubleshooting Microsoft Azure Login Using JamfAAD doc, too. We also added a step to the Company Portal install Policy to just run the `sudo jamf manage` as well.

For anyone who ran into this issue, Jamf emailed me today saying they have a hotfix for Jamf Pro 10.45.1 if needed, or it will be patched in 10.46.0 expected to be released at the end of the month (April 2023).

Yup! Same issue here. For a hot second, I thought it was fixed in 10.45 when I tried it again, and it worked on one of the affected devices. But tried it again on a new device, and it didn't work. A temporary fix is running sudo jamf manage right before the registration, and that seems to work. But glad to hear that the fix is coming in either 10.45.1 or 10.46.

Thank god for this news I have been pulling my hair as well.. sudo jamf manage solves it as a workaround but really hoping it will be permanently fixed in 10.46.

Do we know if this is fixed in 10.46 yet? I havent had a chance to try it out yet.

Still not working for me on 10.46.1

the last days i started to deploy it with the updated company portal (updated was released a few days ago) and configured with the sso extension from microsoft. sudo jamf manage is also a part from the sigin policy in the selfservice, but it look to working fine now for us.

jamf pro on version 10.46.1

any chance someone can post screen shots of their permissions for the following 2 apps created by jamf in azure?

User registration app for Device Compliance

And

Cloud Connector for Device Compliance

You Sir are a magician, thanks for this.

Thanks for this. Been scratching my head all day and running this command has solved it. Legend thanks!