The Phased Deployment Tracking dashboard allows you to track deployment across phases, monitor key statistics, view devices assigned to each phase, and pause deployment if any issues arise.
Accessing the Tracking Dashboard
- Navigate to Resources > Apps > Native Apps > Internal
- Click the hyperlink for the specific application version you want to track.
- On the App Deployment Tracking page, click the assignment name under Devices > Phased Deployment.
Dashboard Overview
The tracking dashboard provides two main views:
Phases Tab
This tab shows how your deployment is progressing across phases, including:
-
Assignment-Level Metrics:
- Total Assigned: Total number of devices assigned to this deployment
- Total Installed: Total number of assigned devices that have successfully installed the application
-
Phase-Level Details:
Click on an individual phase tab to view:
- Phase Started: Date and time when the phase began
- Phase Target: Assignment groups or percentages targeted in this phase
- Exclusion: Assignment groups excluded from this phase
- Assigned: Number of devices assigned to this phase
- Installed: Number of assigned devices that have installed the app
- Install Rate: Percentage of assigned devices with the app installed
- Device List: List of devices assigned to this phase with detailed information
- Progression: Configured progression type and rules (can be updated for upcoming phases)
- Progression History: For phases that have progressed, view how and when a phase progressed. Compare the progression criteria with the metrics collected as the phase progressed.
-
Bulk Actions Available: You can select multiple devices associated with a phase and perform actions such as Install, Remove, and Force Check-In.
Devices Tab
Lists all devices targeted in the deployment along with their assigned phases. This view is useful for viewing devices across all phases in a single list.
Understanding Device Mapping Across Deployment Phases
After a Phased Deployment assignment is published for the first time, devices are gradually mapped to their respective phases as they check in. It can take up to 6 hours for all targeted devices to appear in their assigned phases. As a result, deployment metrics, such as Total Assigned, Total Installed, and other phase‑level statistics, are also updated progressively based on device check-ins.
As devices check in, they are mapped to phases based on the configured phase targets. If a device belongs to multiple Assignment Group phases, it is assigned to the phase configured first in the deployment order. Devices targeted in Progressive Rollout phases are distributed in the ratio of configured percentages. UEM prioritizes mapping devices that have checked in within the last 72 hours to the initial set of Progressive Rollout phases. After that, the devices that haven’t checked in the last 72 hours are mapped to the latter set of Progressive Rollout phases.
Handling newly added devices
Newly enrolled devices that become part of an ongoing Phased Deployment are assigned to phases in the following manner:
- If the device gains membership to an Assignment Group targeted in any group-based phase, it is assigned to that phase.
- If the device gains membership to an Assignment Group not targeted in any group-based phase, it is assigned to the Final phase.
Handling Assignment Group Changes
If a device that was initially part of a Progressive Rollout phase later qualifies for an Assignment Group–based phase, it is automatically reassigned to that phase at its next check-in. If a device no longer meets the requirements for an Assignment Group–based phase but is still included in the phased deployment, it is automatically transferred to the Final phase at its next check-in. These movements of devices between phases do not cause the app to be uninstalled or reinstalled.
Losing assignment to Phased Deployment
If a device is no longer targeted through a Phased Deployment, it is unassigned from its phase at the next check‑in. Additionally, if a device was previously assigned to a Progressive Rollout phase, later loses that assignment, and subsequently becomes eligible again, it is reassigned to the same phase as before.
If a device is part of multiple assignments for the app, priority determines which assignment is used to deliver the app. A device assigned to a yet-to-start phase can receive the app if it has an assignment through another active assignment.
During a phased deployment, the set of devices assigned to a phase and the associated installation rate may change. These changes can occur due to devices being added to or removed from the targeted Assignment Groups, updates to device attributes, new device enrollments, or device unenrollments.
Progressing to the Next Phase
Manual Progression
If configured for manual progression, click Proceed to next phase on the Phase Details view to approve the transition. If you have configured progression to occur at a specific time, you can choose whether to proceed at the configured time or proceed immediately.
Automatic Progression
Automatic progression occurs when all the required automatic progression criteria are fulfilled. If you have configured progression to occur at a specific time, then progression will happen at that time, even if the rules are met earlier.
Additionally, if you prefer not to wait for all automatic progression criteria to be met, you can override the configured rules and manually advance to the next phase. This flexibility helps avoid unnecessary delays in time-sensitive deployments or when earlier phases have demonstrated stability.
For each phase that has progressed, you can view who initiated the progression, whether it is the system or an admin, along with the exact date and time it took place.
Initial Delay
After publishing, deployment does not progress to phase 2 until 6 hours from publish time. This ensures devices have time to check in and get mapped to phases so that automatic progression criteria (if configured) are calculated based on correct assignment information. Admins can override this by manually advancing to the next phase.
Pausing and Resuming Deployment
If unexpected issues arise during a deployment, you can pause the rollout. Pausing immediately halts app installations across all phases, helping prevent further impact while you investigate and resolve the issue. Deployment does not progress to the next phase while it is paused. Additionally, you cannot manually proceed to the next phase in such a state. However, app removals might still occur in a paused state if a device loses its assignment. Once any issues are resolved, you can resume the deployment. Once resumed, the app continues installing from the same phase that was active before the deployment was paused. You can pause and resume a phased deployment any number of times, as needed.
General Availability and Assignment Transition
When deployment reaches its final phase, the app is no longer in a phased rollout and becomes generally available to all assigned devices. You can continue to monitor deployment progress at the phase level for up to 30 days from the start of the final phase.
After these 30 days, phase-level tracking is no longer available. You can continue tracking the deployment using the App Deployment Tracking view instead. Additionally, once the 30-day window is over, the Phased Deployment assignment automatically transitions to an Assignment Group–based assignment. This transition occurs because deployment is no longer performed in phases. Post this transition, admins can edit and manage the assignment like any other Assignment Group–based assignment. Such phased deployment assignments that got transitioned into Assignment Group-based assignments are indicated with an info tip stating that the deployment was initially created as a Phased Deployment.
Was this page helpful?