Troubleshooting Integration (Provider) Health Checks

In the Zip Console, under the ‘Organization Settings’ you will see a tab named ‘Providers’ which gives a view of all the of the third-party providers that are connected to your Zip Console. This will likely cover the IdP, MDM and EDR tools that your organization are using.

 Each provider has additional information to help you see that everything is working correctly, or to flag where something needs to be addressed. The two columns to assess:

1. Health Check - indicates if there is an error that needs to be addressed
2. Licenses in Use - counts the number of licensed assigned to users (in the case of Windows licensing).
   
   

Addressing License Counts

It is important to confirm that you have enough available licenses for all the users in your organization. You will also be notified via the Notification center if you are running low on Microsoft licenses. If this is the case, refer to the following documentation on purchasing additional licenses here.

As a reminder, if Zip is your license reseller, you do not need to take any active steps in purchasing new licenses; we will do this on your behalf.

Troubleshooting Provider Health Checks

Jamf

1. Unmanaged Devices
   Devices can occasionally be marked as “unmanaged,” meaning they appear in Jamf but can’t be managed.
   If this fails, check our our documentation here.
2. Jamf API Credentials Username
   Confirming that we have the ‘zip-service-account’ set up to access customer jamf account.
   If this fails, please reach out to [e-mail] for us to investigate.
3. Jamf API Permissions
   Confirming ‘zip-service-account’ has admin access
   If this fails, please reach out to [e-mail] for us to investigate.
4. Jamf API Ajax Interface is Available
   The Jamf API Ajax interface is needed to take certain actions on devices.
   If this fails, please reach out to [e-mail] for us to investigate.
5. Jamf Cloud Distribution Service Available
   The Jamf Cloud Distribution Service is needed to upload packages to Jamf Pro.
   If this fails, please reach out to [e-mail] for us to investigate.
6. SSO Configuration
   Confirming that SSO configuration has been set up
   If this fails, please reach out to [e-mail] for us to investigate.
7. User-Initiated Enrollment
   Allow users to enroll their computers themselves
   If this fails, please reach out to [e-mail] for us to investigate.
8. Encryption Configuration Profile Set
   If this fails, please reach out to [e-mail] for us to investigate.

Google Workspace current health checks:

1. Google API Permissions
   Confirm that the correct permissions have been granted in Google Workspace to enable Zip to report correct.
   Why it could fail:
   If you haven’t enabled all the permissions, you’ll get an error message. Check these instructions to ensure they are all enabled.
   Note! Some permissions are ‘optional’, and will flag as ‘failing’ if they are not enabled, (even though they may not be required). Again, check the instructions above to confirm.
2. Google Chrome Browser Management Enabled
   If you have not purchased Chrome Browser Cloud Management, then you can dismiss this notification. If you have purchased it, please reach out to [e-mail] for us to help troubleshoot.

Intune current health checks:

1. Microsoft Graph API Permissions:
   Confirm that the API permissions are healthy — which means the integration between Zip <> Entra is healthy.
   Why could it fail:
   Please ensure that permissions are correctly granted from the setup documentation.
   As a note, if there have not been any E3 security licenses purchased yet, then any permissions that relate to device management are going to show as failing. If this is the case, follow the steps above to resolve license purchasing.
2. Microsoft Graph API Credential Not Expiring Soon:
   This will turn unhealthy if the API creds are expiring soon. Please refresh the Zip Service Account credential in Entra.

Entra/Azure current health checks:

1. Microsoft Graph API Permissions:
   Confirm that the API permissions are healthy — which means the integration between Zip <> Entra is healthy.
   Why could it fail:
   Please ensure that permissions are correctly granted from the setup documentation.
2. Microsoft Graph API Credential Not Expiring Soon:
   This will turn unhealthy if the API creds are expiring soon. Please refresh the Zip Service Account credential in Entra.

CrowdStrike current health checks:

1. CrowdStrike Portal Users
   Confirming that a team member has been added to access the CrowdStrike portal
   What to do: reach out to [e-mail] for a user to be added.

Email Alerts current health checks:

1. Invalid Email
   This health check confirms that the emails entered to receive alerts are valid emails.
   If it fails, please confirm the emails are correct by re-entering them in the provider configuration. If this doesn't resolve the issue, contact [e-mail].
2. SendGrid Down
   Checks if SendGrid, which email alerts are sent through, is experiencing a service outage.
   If this is failing, you can check SendGrid for more information on the outage.

Slack Webhook current health checks:

1. Slack Webhook Valid Format
   Checks that the Slack webhook matches the expected format, https://hooks.slack.com/services/T_____/B_____/___________.
   If this is failing, please try entering in your webhook again.
2. Slack Webhook Accessible
   Checks if your webhook can currently be reached
   If this is failing, please try entering in your webhook again.