Create it-service-company.md (#41994)
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
This commit is contained in:
co-authored by
Mike Thomas
parent
b87bf3b826
commit
76e9e2a81b
@@ -0,0 +1,72 @@
|
||||
# IT services company builds zero-touch workflows with Fleet
|
||||
|
||||
This IT services company provides endpoint management and security solutions for enterprise customers. As it expands its own environment, the team wants device management that is secure by default and easy to automate.
|
||||
|
||||
Fleet helps the company build zero-touch deployment workflows and manage device state through code.
|
||||
|
||||
## At a glance
|
||||
|
||||
* **Industry:** IT services and endpoint management
|
||||
|
||||
* **Devices managed:** 100+ Windows devices, expanding to macOS and Linux
|
||||
|
||||
* **Primary requirements:** Zero-touch deployment, GitOps workflows, osquery visibility
|
||||
|
||||
* **Previous challenge:** Legacy tools could not support secure, automated deployments at scale
|
||||
|
||||
## The challenge
|
||||
|
||||
Before Fleet, the company relied on legacy tools that were not built for zero-touch, secure laptop deployment.
|
||||
|
||||
The team needed better visibility into device state and a more automated way to manage credentials, policies, and user transitions. Existing tools relied on manual workflows, created friction, and could not support a secure-by-default model at scale.
|
||||
|
||||
## The evaluation criteria
|
||||
|
||||
The team focused on three capabilities:
|
||||
|
||||
1. **Zero-touch deployment**
|
||||
Automate device setup from the moment a machine is unboxed.
|
||||
|
||||
2. **GitOps workflows**
|
||||
Manage device state programmatically rather than through manual UI actions.
|
||||
|
||||
3. **osquery integration**
|
||||
Use deep system-level data to drive security workflows.
|
||||
|
||||
## The solution
|
||||
|
||||
Fleet gave the team a platform for automated deployment, identity-aware workflows, and real-time visibility.
|
||||
|
||||
The company used the Fleet API to rotate Recovery Lock passwords, manage hidden admin accounts, and respond to identity changes without manual intervention. Integrations with Okta also helped automatically remove deactivated users, reducing the risk of leftover access on managed devices.
|
||||
|
||||
The open-source model was important because it allowed the team to inspect the code and verify behavior directly.
|
||||
|
||||
## The results
|
||||
|
||||
Fleet gave the team a stronger foundation for secure deployment and lifecycle management.
|
||||
|
||||
* **Better zero-touch workflows:** New devices can be set up with more consistency and less manual work.
|
||||
|
||||
* **Faster security response:** Identity and device changes can trigger action quickly.
|
||||
|
||||
* **Simpler management:** The team can centralize security policies across operating systems.
|
||||
|
||||
## Why they recommend Fleet
|
||||
|
||||
For this company, the biggest benefit is zero-touch visibility. Fleet helps the team build automated workflows that are more secure, more scalable, and easier to verify.
|
||||
|
||||
## About Fleet
|
||||
|
||||
Fleet is the single endpoint management platform for macOS, iOS, Android, Windows, Linux, ChromeOS, and cloud infrastructure. Trusted by over 1,300 organizations, Fleet empowers IT and security teams to accelerate productivity, build verifiable trust, and optimize costs.
|
||||
|
||||
By bringing infrastructure-as-code (IaC) practices to device management, Fleet ensures endpoints remain secure and operational, freeing engineering teams to focus on strategic initiatives.
|
||||
|
||||
Fleet offers total deployment flexibility: on-premises, air-gapped, container-native (Docker and Kubernetes), or cloud-agnostic (AWS, Azure, GCP, DigitalOcean). Organizations can also choose fully managed SaaS via Fleet Cloud, ensuring complete control over data residency and legal jurisdiction.
|
||||
|
||||
<meta name="articleTitle" value="IT services company builds zero-touch workflows with Fleet">
|
||||
<meta name="authorFullName" value="Irena Reedy">
|
||||
<meta name="authorGitHubUsername" value="irenareedy">
|
||||
<meta name="category" value="case study">
|
||||
<meta name="publishedOn" value="2026-03-18">
|
||||
<meta name="description" value="An IT services company builds zero-touch device workflows with Fleet, automating deployment and security.">
|
||||
<meta name="useBasicArticleTemplate" value="true">
|
||||
Reference in New Issue
Block a user