A Cradle Desktop update is coming, and you need to grand new scopes so that your users will be able to sign into the Cradle Desktop app.
View in browser

Hi there,

 

This is an important email regarding the authentication of users who log into Cradle Desktop. You're receiving this because you're an administrator of Cradle for your organisation, and you log in with Microsoft. 

 

What change is being made?

We have updated the app registration with Microsoft, which Cradle Desktop uses. When any of your users log into the app for the first time after updating to the next version (3.9.1) of the Desktop App, they will be prompted to grant permissions to Cradle Desktop to access their Microsoft Account.

 

Who does this affect?

All users who log into Cradle Desktop using Microsoft. Other applications (Android, iOS and the Web Portal) remain the same, as do users who log in with Google. 

 

Why have we made this change?

We are releasing an update to Cradle Desktop shortly that will sync presence between Cradle Desktop and MS Teams. We were not able to release this functionality on our previous app registration. 

 

What changes?

Not much! The only difference that users will face on an ongoing basis is that when signing in, the user will be redirected to a browser to authenticate, and they will be presented with this prompt (once signed in):

Screenshot 2025-07-03 at 08.59.19

Your users need to click Continue. Cradle Desktop can then sign in. They can safely close the tab in their browser once they have clicked Continue. They may be prompted by their browser to let the website open 'Cradle Desktop'. 

 

What you need to do

If you have controls on your Microsoft Entra Tenant that prevent users from accepting new scopes when logging in with their associated MS user account, you may need to accept new scopes for your entire organisation.

 

The new Application (Client) ID for Cradle Desktop is:

53ffeedf-e47a-466f-97a8-25de7d14fc14

The scopes requested are:

  • Contacts.Read (this allows the user to access their Outlook contacts from within Cradle Desktop)
  • offline_access (this allows the app to stay logged in across sessions)
  • openid (this allows the app to log in)
  • Presence.ReadWrite and Presence.Read.All (this allows the app to sync presence with MS Teams)
  • profile (this allows the app to view the user's name and email details)
  • User.Read (this allows the app to verify that the user matches a Cradle user)

Here is the MS Entra help page for granting admin consent to an enterprise application. 

 

If the domain through which you received this email is your MS Entra domain, you can click on this link to grant this permission: https://login.microsoftonline.com/cradle.io/adminconsent?client_id=53ffeedf-e47a-466f-97a8-25de7d14fc14

 

You will be greeted with this screen. Please click Accept. 

Screenshot 2025-07-03 at 09.35.38

We would suggest that you grant this permission prior to updating any users to 3.9.1 of Cradle Desktop. You can wait until the app is released, at which point you will be prompted to grant this permission. If users are unable to grant Cradle the required permissions on their own, they won't be able to log in. 

 

Cradle Desktop 3.9.1 will be rolled out over the next week, with macOS and Linux releases starting today (3 July), Microsoft Windows exe-based installs updating early next week (7 July), and MS Store and appx versions updating late next week (10 July). 

 

A product release email will follow the update to detail the features available in 3.9.1. Please submit a support ticket or reply to this email if you need further help. 

 

Thanks,

 

James McCarthy Toia

CEO

Cradle Limited, 20 Crummer Road, Grey Lynn, Auckland 1021, New Zealand, +64 9 887 9333

Unsubscribe Manage preferences