India's largest passenger vehicle manufacturer · 2M+ annual vehicle sales · Automotive & manufacturing

Turning a nationwide fleet of official phones into one secure, policy-controlled system.

9:41 OFFICIAL DEVICE WATERMARK APPLIED SHARE: OFF Azure AD sign-in Sync to server MDM ENROLLED Policy: active DELETE: LOCKED User-end disabled
The brief, as we understood it
“
Enable our official mobile devices with apps that strengthen data security and communication - without adding friction to how our people already work.
- Our reading of the brief handed to Milleniance at the start of the engagement
01 - The challenge

Thousands of company-issued phones. No single, enforceable policy.

The client - a multi-billion dollar automotive manufacturer selling 2M+ vehicles a year, with roughly 40% of the Indian passenger vehicle market - equips a large number of field and operational staff with official Android devices for daily work. Each of those devices is a small, unmanaged risk: photos and videos captured on the job can be copied, shared or deleted with no record of it happening, and nothing was stopping sensitive operational media from leaving the organisation through a personal chat app or a memory card.

At the same time, reaching that same fleet with anything - a policy update, a safety notice, an internal survey - meant relying on scattered channels with no way to confirm who had actually seen it.

  • No consistent control over photo and video capture on official devices
  • Data sharing and deletion left entirely to individual discretion
  • No unified way to push notices, updates or surveys to the fleet
UNMANAGED DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE
02 - The approach

Ship in phases the business can actually absorb.

Rather than one large release, the build was sequenced into phases that solved the most urgent risk first - media governance - before layering in sync, identity and communication. Every phase was scoped, delivered and accepted before the next began, so the client was never blocked waiting on a single, all-or-nothing launch.

Each phase was reviewed jointly against agreed criteria before sign-off, and the whole rollout was designed to sit cleanly inside the client's existing Microsoft Intune device-management setup, rather than asking the organisation to change how it already managed its fleet.

  • Phase 1 - capture-time data security and controlled deletion
  • Phase 2 - governed connectivity and automatic server sync
  • Phase 3 - the internal communications layer, fleet-wide
PHASE 1 Data security PHASE 2 Sync & connectivity PHASE 3 Communication ACCEPTED ACCEPTED LIVE
03 - What we built

One secure app. Four capabilities working as a single system.

Watermarking & media governance
Every photo and video captured through the app is watermarked at the point of capture, with in-app deletion disabled at the user end so records can't quietly disappear.
Governed connectivity & sync
Data sharing is disabled by default while Bluetooth stays available for the functions that need it, and captured data syncs to company servers automatically on a regular schedule.
Enterprise identity
Sign-in runs through Active Directory and Azure AD, so device access follows the same identity and access rules as the rest of the organisation's systems.
Internal communications suite
Admin-managed notifications, app theming, wallpapers, a home-screen carousel and surveys, all built and reportable from a central backend rather than scattered tools.
Built on

A stack chosen to sit inside the client's existing device-management setup, not replace it.

Android (native) Microsoft Intune MDM Azure Active Directory Admin backend & reporting Push notifications Managed cloud hosting
05 - Where it stands today

A fleet-wide system that's been running quietly in the background since 2021.

3
Delivery phases, each accepted before the next began
3yr
Ongoing engagement covering support, hosting and upgrades
0
Version cap on Android upgrades under the maintenance plan
1
Unified system replacing scattered device-communication tools

"If your fleet of company devices is still governed by policy documents instead of the software itself, that's usually the first thing worth fixing."

Let's see if we're the right fit

Thirty minutes with a senior mobility architect, before either of us commits to anything.

No sales deck, no discovery call with someone who hands you off afterwards. We look at your device fleet, data risk and what "secure" actually needs to mean for your team. We respond within one business day.

Talk to a Senior Mobility Architect →