AirWatch Application Configuration for Microsoft Office 365 Mobile Apps
Microsoft Office 365 mobile apps give Australian organisations a practical way to keep staff productive across iPhone, iPad and Android devices. Word, Excel, PowerPoint, Outlook, OneDrive and Teams can support office-based teams in Sydney, mobile workers in Perth and field staff travelling between regional sites. However, a productive mobile experience still needs consistent configuration, access controls and data protection.
AirWatch, now associated with VMware and commonly delivered through the Workspace ONE UEM platform, helps administrators manage these requirements from a central console. IT teams can deploy Microsoft apps, apply managed settings, separate business information from personal content and respond quickly when a device is lost or a worker leaves the organisation.
Preparing Office 365 Apps For Managed Deployment
Begin by identifying which Microsoft mobile applications employees actually need. A finance team may require Excel and Outlook, while a construction business could prioritise Teams, OneDrive and mobile document review. Avoid assigning every application to every user, as unnecessary software increases support demands and can complicate data governance.
In the AirWatch or Workspace ONE UEM console, administrators can add the approved Office applications from the relevant enterprise app store, then assign them to smart groups. These groups may be based on department, role, operating system, ownership model, location or compliance status. For example, users in a Melbourne head office might receive the complete Office suite, while a regional service team receives Outlook, Teams and OneDrive.
Application distribution can be configured as automatic or on demand. Automatic installation suits essential tools, whereas optional deployment through an enterprise catalogue gives employees some control. Set minimum operating system versions, licensing requirements and app update rules before publishing the assignment. Microsoft 365 licensing remains a separate consideration: UEM can manage delivery and policy, but it does not replace the organisation’s Microsoft subscription or user entitlements.
Configuring Managed App Settings
Managed app configuration allows administrators to apply approved settings without asking employees to enter them manually. The available keys vary by application and platform, so test each Microsoft app against the current Microsoft documentation and the version approved in your environment. Configuration may cover account sign-in behaviour, document storage locations, restrictions on copying content and access to connected services.
For example, Outlook can be configured to use a company account and restrict movement of corporate email into unmanaged applications. OneDrive settings can encourage business files to remain within the organisation’s approved storage environment. Office applications can also be governed through controls that limit opening company documents in unauthorised apps or saving them to personal cloud accounts.
The exact options differ between iOS and Android. Android Enterprise generally provides a strong framework for managed application settings, while Apple devices use managed app configuration delivered through MDM. Use separate profiles where platform behaviour differs rather than forcing one generic policy across both systems. This reduces confusing prompts and makes troubleshooting easier for a help desk in Brisbane, Adelaide or a remote support centre.
Microsoft security controls should be coordinated with UEM settings. Conditional access through Microsoft Entra ID, Microsoft Defender and Microsoft 365 security policies may affect whether a user can sign in. A successful deployment therefore requires testing the full sign-in path, including multifactor authentication, device compliance, certificate requirements and network conditions.
Balancing Productivity, Privacy And Compliance
A sound mobile policy protects company information without treating every personal device as if it were corporate property. Australian organisations must consider the Privacy Act and the Australian Privacy Principles, especially when personal devices are enrolled in a bring-your-own-device programme. Employees should understand what information AirWatch can collect, what administrators can see and what actions can be taken remotely.
For BYOD users, application-level controls are often preferable to broad device restrictions. App protection settings can limit copy and paste, screenshots, printing, sharing and opening documents in unmanaged applications, depending on the capabilities of the operating system and Microsoft app. Selective removal of corporate data is also less disruptive than wiping an entire personally owned phone.
Corporate-owned devices can support stronger controls. A company-issued iPad used by a healthcare, mining or logistics team may be locked to approved applications, encrypted, monitored for compliance and automatically configured with certificates. Lost devices can be locked or wiped, while an employee’s access can be revoked when their employment ends.
Australian data handling expectations can be particularly important for organisations working with government, health or financial information. Consider where diagnostic data, backups and Microsoft 365 content are stored, and document the roles of local providers, cloud services and offshore support teams. Requirements may also align with the Essential Eight, industry rules or contractual data residency obligations.
| Management area | AirWatch or Workspace ONE UEM role | Microsoft 365 role | Practical Australian use |
|---|---|---|---|
| Application delivery | Assigns and distributes approved mobile apps | Supplies the Office app licences and services | Deploy Teams and Outlook to field staff across New South Wales |
| App configuration | Sends managed settings to supported applications | Defines available configuration keys and behaviours | Standardise OneDrive and Outlook settings across corporate iPhones |
| Identity and access | Applies device and compliance context | Handles Microsoft Entra ID sign-in and conditional access | Require compliant devices before accessing customer records |
| Data protection | Enforces device, app and ownership policies | Provides Microsoft security and information protection controls | Separate work documents from personal apps on BYOD devices |
| Lifecycle management | Updates, removes or blocks applications and devices | Retires accounts, content access and service licences | Remove access promptly when a contractor finishes a project |
Testing Policies Before Broad Rollout
Create a pilot group that reflects real working conditions rather than testing only on an IT administrator’s device. Include iOS and Android users, corporate-owned and BYOD devices, older supported hardware and users who work with poor connectivity. A FIFO worker near a mine site, a sales representative on the road and an office-based employee may experience very different deployment outcomes.
Test installation, sign-in, multifactor authentication, document editing, attachment handling, Teams meetings and OneDrive synchronisation. Check whether users can move information into consumer apps, save content locally or share documents through personal accounts. Confirm that a device becoming non-compliant produces the intended result without blocking legitimate work unnecessarily.
Battery use, mobile data consumption and roaming costs deserve attention in Australia’s large geographic environment. A policy that works well on an office Wi-Fi network may create frustration for workers travelling through regional Queensland or Western Australia. Schedule large application updates sensibly and avoid forcing repeated downloads over mobile connections.
Record the expected user experience for each policy. A clear service desk script should explain why a sign-in is blocked, how a device becomes compliant and which actions are available after a lost phone is reported. Plain Australian workplace language, such as “company phone”, “work account” and “approved app”, is often more effective than unexplained security terminology.
Operating The Environment Over Time
Application configuration is an ongoing management task rather than a one-off deployment. Microsoft changes mobile application features, configuration keys and authentication requirements, while Apple and Google regularly update their operating systems. Review policies whenever a major Office release, operating system update or identity change is introduced.
Use compliance dashboards and application reports to find devices with outdated apps, failed installations or inactive users. Set a review cycle for smart groups, assignment exclusions and retired applications. Remove duplicate profiles and old test settings, as conflicting configurations can create inconsistent results that are difficult to diagnose.
A staged release process reduces operational risk. Test updates with IT and business champions, expand to a small production group, then release to the wider workforce. Keep a rollback plan for changes involving Outlook access, document sharing or Teams authentication. For critical services, record the previous configuration and the administrator responsible for approving restoration.
Organisations can also use AirWatch reporting to support audits and internal reviews. Document application ownership, policy purpose, data access, retention expectations and approval dates. This evidence helps demonstrate that mobile access is governed deliberately, which is valuable when reviewing privacy obligations, customer contracts or Essential Eight improvement work.
Recommended Configuration Practices
- Use smart groups to match Office app assignments with role, ownership type, platform and business location.
- Apply the least restrictive policy that protects corporate information, especially on personally owned devices.
- Test managed app configuration separately on iOS and Android before production deployment.
- Combine UEM compliance with Microsoft Entra ID, multifactor authentication and Microsoft 365 security controls.
- Maintain a documented review and rollback process for application, operating system and identity changes.
A well-designed AirWatch deployment can make Office 365 mobile access feel straightforward to employees while giving administrators meaningful control over business information. The strongest results come from treating application delivery, identity, privacy and support as one service rather than as separate configuration tasks.
Organisations assessing their current approach can compare Workspace ONE UEM capabilities, package options and supported integrations before selecting a rollout model. AirWatch also promotes a fully functional 30-day free trial, giving Australian IT teams an opportunity to test Office app deployment, managed settings, compliance workflows and BYOD controls with representative devices before committing to a broader programme.