Chipmunk First-Time Configuration Wizard

Once you’ve completed the prerequisite setup steps and deployed the Chipmunk appliance from the Azure Marketplace, it’s time to configure the system for first use. This is the final step of the four-step Chipmunk setup - by the end of this page the appliance is operational and ready to start archiving disabled users.

This page guides you through the initial configuration process after deployment. You'll need the values collected in App Registration, Azure Storage Setup, and DNS & TLS Certificate Configuration - have them in front of you before starting the wizard.

Step 1: Prepare Before Deployment

Make sure you have the following details ready before deploying the appliance:

• Azure Subscription
• Resource Group
• Virtual Network (VNet) and subnet
• Hostname you will assign to the appliance (e.g. chipmunk.yourcompany.local)
• Azure App Registration (Client ID, Secret, Tenant ID)
• Azure Blob Storage SAS URL
• TLS Certificate files (PEM format), or plan to generate a self-signed certificate
• Entra ID Group name (e.g. chipmunkadmins) - only members of this group will be able to access the dashboard

If you haven’t created the admin group yet, follow the guide here:
→ How to create the admin group

All of these values were configured or generated during the previous setup steps.

Step 2: Deploy from Azure Marketplace

1. Open the Azure Portal

2. Go to Create a Resource

3. Search for Chipmunk - Automated User Archiving

4. Click Create

5. Fill in:

• Subscription, Resource Group
• Appliance Name (e.g., chipmunk)
• Region and VNet/Subnet

6. Complete and deploy the resource

Deployment typically takes 3–5 minutes.

Step 3: Access the Setup Wizard

Once the appliance has finished deploying, open your browser and go to:
http://chipmunk.yourdomain:3000 (port 3000 is only required for initial setup)

→ You’ll see the Chipmunk Setup Wizard.

Step 4: Enter Configuration Details

The setup wizard will prompt you to enter:

• Tenant ID – from Azure App Registration.
• Client ID – Application ID.
• Client Secret.
• Blob SAS URL – from Storage setup.
• Azure AI Endpoint and Key – (optional, for document summarisation).
• TLS Certificate – upload PEM files if not using self-signed.
• DNS hostname for this appliance – e.g., chipmunk.yourdomain.
• Admin Group Name – the exact name of your Entra ID security group (e.g., chipmunkadmins).

Only users who are members of this group will be able to log in to the Chipmunk dashboard.

Step 5: Finish Setup & Restart

• Click Submit.
• Chipmunk will apply your configuration and restart the appliance.
• Wait 2 full minutes for the system to restart and apply TLS settings.

After restart, your browser will be redirected to:
https://chipmunk.yourdomain (HTTPS on port 443 for all normal access after setup)

You may need to accept a certificate warning if you chose the self-signed certificate option.

Step 6: Log In and Verify

Once redirected, you’ll land on the Chipmunk dashboard login page.

You can now:

• Monitor archives
• View archived users
• Restore data as needed

Troubleshooting

If you are not redirected after 2 minutes:

• Manually try: https://chipmunk.yourdomain
• Check if the appliance is reachable via DNS
• Ensure your firewall allows ports 443 and 3000 internally

Need help? Visit Support or contact support@smikar.com

Common questions

Q: I submitted the wizard but the appliance won't redirect to HTTPS - what's wrong?

• The most common cause is a TLS certificate / DNS mismatch. The CN or SAN on your uploaded PEM certificate must exactly match the DNS hostname you entered (case-sensitive). Re-check both, then either upload a corrected cert or change the DNS hostname to match the cert. The DNS & TLS Certificate Configuration page covers this in detail. If you're using the self-signed fallback, the browser warning is expected; click through it.

Q: I'm in the admin group but I still can't log in.

• Three things to check, in order: (1) the admin group name was entered exactly (case-sensitive, no leading/trailing spaces), (2) your user is a direct member of that group, not a member of a nested group (Chipmunk currently checks direct membership only), and (3) admin consent was granted on the App Registration permissions in App Registration. If all three look right, the appliance logs covered on Monitoring & Logs will show the exact reason the sign-in was rejected.

Q: Can I re-run the setup wizard later if I made a mistake?

• For most values yes - open the Configuration page in the dashboard and update individual fields without re-running the full wizard. The DNS hostname and TLS certificate can also be updated there. The one thing that's painful to change after setup is the storage account / SAS URL, because old archives stay in the original container; switching containers means new archives go to the new one but old data lives in the old.

Q: The wizard takes a Blob SAS URL and an Azure AI key - is the AI part required?

• The Azure AI fields are optional. If you provide them, Smart AI Search is available across archived content and the dashboard's AI-powered insights light up. If you leave them blank, archive and restore still work normally; you just lose the AI search and summarisation features. You can add them later via the Configuration page.

Q: How long does the appliance take to come up after I submit?

• Plan for at least two minutes. The wizard applies your configuration, restarts the appliance, and brings it up on HTTPS (port 443). If you watch the Activity Monitor page after sign-in, the first archive jobs typically kick off within an hour as Chipmunk polls Entra ID and finds disabled accounts to process.