Overview
Our Intune automated application packaging service ensures that customers always have access to the latest application versions. When a new version is detected in our back catalogue, it is automatically packaged and uploaded to customers consuming the app. However, applications are not assigned immediately to customers upon upload. This article outlines the assignment deferral process and how customers can configure assignment delays to support testing through pilot, UAT (User Acceptance Testing), and production environments.
Assignment Deferrals
To ensure application stability and compatibility, we have a built-in minimum one-day delay between the upload and assignment of new application versions. This delay allows our app packaging team to thoroughly test new releases to confirm they function as expected.
Customers can also configure assignment deferrals for specific deployment stages to conduct their internal testing and rollout processes. These stages typically include:
-
Pilot: Limited group testing
-
UAT: Broader testing for user acceptance
-
Production: Full deployment across the organisation
Customisable Assignment Delays
Customers have the flexibility to request custom assignment delays for each stage of their deployment process on a per-application basis. Below is an example configuration:
| Deployment Stage | Assignment Delay |
|---|---|
| Pilot | 1 day |
| UAT | 3 days |
| Production | 5 days |
Key Features:
-
Per Application Customisation: Assignment delays can be customised for each individual application.
-
Customer-Specific Needs: Delay values can be tailored to each customer’s unique deployment strategy.
Considerations for Extreme Delays
While assignment deferrals are highly customisable, customers should be mindful of the potential impact of extreme delays:
-
Version Lag: Applications with frequent updates (e.g., every three days) may cause production environments with a nine-day assignment delay falling behind by three versions.
-
Security and Stability: Delays in applying the latest versions may expose customers to unresolved issues or security vulnerabilities.
Recommendation:
We recommend customers regularly review their assignment delay settings to balance thorough testing with timely access to the latest application updates.
Best Practices for Assignment Deferrals
-
Pilot Testing: Keep the pilot group delay minimal (e.g., 1 day) to catch issues early.
-
Gradual Rollout: Use moderate delays for UAT and production to provide adequate testing time without excessive delays.
-
Review Frequency: Monitor the frequency of application updates and adjust delay settings accordingly.
By leveraging assignment deferrals, customers can create a structured and reliable testing and deployment process, ensuring stable application rollouts that meet their organisational requirements.