IntuneBrewTroubleshooting
Fixes for sign-in problems, uploads that won't start or don't finish, and apps that don't install as expected.
Find the message you see below. Most error messages in the portal also show numbered steps and a Technical reference; include that reference if you contact support.
Signing in
Stuck in a sign-in loop
An outdated session saved in the browser can send you back to sign-in repeatedly.
- Open the portal in a private (InPrivate or Incognito) window and sign in.
- If that works, clear the site data for
intunebrew.com(cookies and local storage) in your normal browser and sign in again. - If you use several Microsoft accounts, sign out of the ones you don't need for IntuneBrew in the Microsoft sign-in window.
"Your Microsoft session has expired"
A banner at the top of the portal says your session expired. Select Sign in again; your data reloads afterwards. Buttons that need Microsoft, such as Retry, stay disabled with Sign in again first until you do.
If the banner says Microsoft could not refresh your session in the background, your browser usually holds a Microsoft session for a different account. Sign in again and pick the account you use for Intune.
"Your browser blocked the Microsoft sign-in window"
IntuneBrew signs in through a pop-up window. Allow pop-ups for www.intunebrew.com and try again.
"Microsoft needs you to sign in again"
Your organization's Conditional Access policy requires multi-factor authentication or another check. Sign in again and complete it.
"An administrator must approve this permission for your organization"
Your tenant doesn't let users consent to apps themselves. Ask an Entra administrator to sign in to IntuneBrew once and approve the permission for the whole organization. See Permissions.
Everyone new is a viewer
That's expected. Colleagues who sign in without an invitation join as viewers. See Team access.
An upload won't start
When an upload is blocked before it starts, the portal says No workflow started, and nothing was changed in Intune. Fix the cause and start the update again.
| Message | Cause | Fix |
|---|---|---|
| Your Microsoft session expires too soon | Uploads need a session with at least 45 minutes left. | Sign in again, then retry. |
| Microsoft app-management consent is missing | DeviceManagementApps.ReadWrite.All hasn't been granted. | An Entra administrator grants consent; then sign out and back in. |
| Your account cannot manage Intune apps | Your Entra account has no Intune role that can manage apps. | Ask for the Application Manager or Intune Administrator role, or a custom role with Mobile apps permissions. |
| A viewer role cannot perform this action, or Failed to start the upload | Your IntuneBrew role is Viewer. | Ask an owner to make you an Administrator. See Team access. |
| This app already has an active upload | Someone started this app in the last 20 minutes. | Wait for it to finish; select View upload status. |
| The package cannot be downloaded, or returned a web page instead of an installer | The vendor's download link changed or is down. | Try again later, or select Report package issue. |
| The app is no longer in the upload catalog | The app was removed from the catalog. | See App catalog. |
| Intune readiness could not be verified, or The upload worker is not ready | A temporary problem reaching Microsoft or IntuneBrew's upload service. | Select Check again. |
A yellow banner across the portal saying Your Microsoft Entra ID account is not allowed to manage apps in Intune means the same as Your account cannot manage Intune apps. Select Check again after your role was assigned.
An upload fails or stops
| Message | What happened | Fix |
|---|---|---|
| Microsoft requires additional verification | Conditional Access asked for another check mid-upload. | Select Verify and retry. |
| Your Microsoft session needs to be renewed | The session ended during the upload. | Select Sign in and retry. |
| Intune denied the upload | Intune refused to create the app or its content. | Check the account's app-management role, admin consent, Intune licensing and scope tags. Retrying won't help until that's fixed. |
| Microsoft Intune is temporarily unavailable, or Intune could not prepare upload storage | A temporary Intune or Azure Storage problem. | Select Retry upload. |
| The upload stopped reporting progress | No progress for 20 minutes. | Select Retry upload. |
"The new app could not be verified" or "Intune is still processing the new app"
The new version reached Intune, but IntuneBrew couldn't confirm it finished processing. To stay safe, it left the previous version and its assignments unchanged. Open the new app in Intune: if it shows the new version, assign it or carry over assignments yourself. If it's incomplete, delete it and run the update again.
"Assignment verification needed" or "Previous versions preserved"
The update itself succeeded. See Carry over assignments.
Apps on Macs
Intune says the app isn't installed, but it is
The app on the Mac probably updated itself and no longer matches the version in Intune. Turn on Intune's Ignore app version for the app; see Version detection.
The installation fails on devices
Look up the error code in the Intune admin center under Apps → macOS → the app → Device install status. The blog article Troubleshooting common macOS app deployment issues explains the common codes.
Dashboard and reports
| Message | Fix |
|---|---|
| Permission needed / Grant access to device inventory | Select Grant access and approve the read permission in the pop-up. If your organization requires an administrator to approve it, ask one to grant admin consent. |
| Your account cannot read Intune devices / No Intune access | The permission is granted, but your Intune role can't read devices. Ask for Intune Administrator or a custom role with Managed devices: Read. |
| Access denied by Microsoft | Your Intune role can't read Intune apps. Ask an Intune administrator for a role that can. |
| Microsoft is not responding / Connection problem | Wait a moment and select Retry. |
PowerShell tool
| Problem | Fix |
|---|---|
IntuneBrew is not recognized | On macOS, add ~/.local/share/powershell/Scripts to your PATH. See Install and connect. |
| A parameter from these docs is not recognized | Your installed version is older. Use version 1.1.0 from GitHub. |
| The authenticated tenant does not match the requested configuration | tenantId in your configuration file must be the tenant GUID of the app registration's tenant. |
| The script stops after connecting with an app registration | A required permission is missing or not admin-consented. See Permissions. |
| SHA256 hash of the downloaded file does not match the expected value | The downloaded installer doesn't match the catalog checksum. Don't bypass it; try again later or report it on GitHub. |
Still stuck?
- Email support@ugurlabs.com with the time, the app, your account, and the Technical reference from the error.
- Report catalog or PowerShell problems on GitHub.