If your organization enforces SSO-only authentication, sharing a build with an external freelancer, QA studio, or partner has always meant a compromise: either create exceptions in your identity configuration or ask external users to go through an authentication flow they don't have access to.

Neither option is acceptable when compliance is non-negotiable.

OTP (One-Time Password) access solves this. It lets you grant temporary, identity-verified access to any external user — at the publication level — without touching your global SSO configuration.

⚙️ Key Capabilities

📧 Email-based allowlist

Add the email addresses of authorized external users directly to a publication. No Applivery account or SSO enrollment required on their end.

⏱️ Time-limited, single-use codes

OTPs are valid for 5–10 minutes and cannot be reused. Each access attempt requires a fresh code, ensuring no credentials can be shared or replayed.

🔁 Single-use access

Optionally remove an email from the allowlist after the first successful download, enforcing strict one-time access. Re-adding is always possible if needed.

⏳ Temporary user lifecycle

OTP users are created automatically and auto-deleted after 30 days. Existing workspace users are never counted twice.

🔔 New build notifications

When a new build is published, OTP users on the allowlist can receive a notification email with a fresh code — no need to re-request access manually.

📅 Combine with Expiring Publications

Pair OTP access with an expiring publication for a fully time-bounded and identity-verified external sharing flow, with zero manual cleanup.

📌 Use Cases

• External freelancers or contractors: One-time build review without creating permanent accounts.
• External QA studios: Time-limited access to a beta without relaxing global authentication.
• Partner or customer previews: Share a specific build securely with a named list of recipients.
• SSO-enforced organizations: Distribute externally without creating SSO exceptions or compromising your identity policy.

📚 You can learn more about OTP by following this link.

If you have any questions or need more information, please contact your Customer Success Manager.

Starting in April, we will introduce a new limit on the maximum number of publications per app within App Distribution. This change helps keep app distribution organized and aligned with each subscription plan.

New limits per plan

📦 Starter: up to 3 publications per app

📦 Essentials: up to 5 publications per app

📦 Startup: up to 15 publications per app

📦 Business: up to 30 publications per app

📦 Enterprise: up to 50 publications per app

These limits apply to the number of publications that can be associated with a single app in App Distribution.

👉🏻 To optimize the use of your App Publications, check out our best practice recommendations.

If you have any questions or need more information, please contact your Customer Success Manager.

We’re excited to announce that you can now manage Private DNS settings on fully managed Android devices (Android 10 and above) through AMAPI. This feature allows you to control how devices connect to DNS servers securely and enforce network policies across your fleet.

Key Details

🌐 Private DNS Mode Options:

• USER_CHOICE: The user can configure private DNS.
• AUTOMATIC: The device automatically uses the network-provided DNS over an encrypted connection. Users cannot modify this setting. Supported on fully managed devices and work profiles on company-owned devices.
• SPECIFIED_HOST: The device uses only the DNS server specified in Private Dns Host. Users cannot change this setting. If you select this mode, Private Dns Host must be set.

🛠️ Private DNS Host:

• Optional field required only when Private DNS Mode is set to SPECIFIED_HOST.
• The hostname must correspond to a supported DNS server. Non-compliance is reported if the host is invalid, the device is not on a network, or other restrictions apply (e.g., unsupported Android version or management mode).

⚠️ Non-Compliance Details:

• Devices not meeting the requirements will report a NonComplianceDetail, specifying the reason (e.g., invalid host, unsupported management mode, Android version <10, or pending network connection).

This new setting helps you enforce secure network connections, control DNS usage, and maintain compliance across your Android fleet.

We’re sharing an important update regarding a recent Android Management API change. An experimental API field, allowedDaysWithoutUpdate, was unintentionally exposed and will be reverted next week to ensure proper platform behavior.

The rollback is scheduled to be fully deployed by Friday, March 6.

Impact

Once this change is live, any policy that includes this field will be rejected in its entirety.

Action required

If you have started any integration or release that relies on this field, please remove it from your policy configurations to remain aligned with the supported APIs.

We want to inform you that Skype for macOS has been removed from the Applivery macOS App Catalog.

Microsoft officially discontinued support for Skype over a year ago and transitioned its communication platform to Microsoft Teams, which is now the recommended and actively maintained solution.

🔎 What This Means

• ❌ Skype for macOS is no longer available in the catalog
• 🔄 Microsoft Teams is the supported alternative
• 🛠️ Existing deployments of Skype will not receive updates or support

We strongly recommend migrating any remaining Skype workflows to Microsoft Teams or another alternative solution to ensure continued functionality, security, and support.

We’re excited to introduce Segments in Device Management, enabling more powerful and flexible automation workflows across your device fleet.
​
With Segments, you can dynamically organize and act on devices using structured grouping logic — helping IT teams scale operations with greater precision and efficiency.
​

🚀 What You Can Do

• 🎯 Create dynamic device groupings based on defined criteria.
• ⚙️ Automate policy and configuration workflows more effectively across the fleet.
• 🔄 Keep device targeting always up to date as attributes change.
• 🧠 Reduce manual management with rules-based segmentation.

This new feature strengthens your ability to manage large fleets by ensuring the right actions are applied to the right devices at the right time.

​🔍 Why It Matters

Segments enable a more data-driven and automated approach to Autonomous Endpoint Management. By dynamically grouping devices, administrators can streamline deployments, enforce policies with precision, and maintain consistency across evolving environments.

👉🏻 You can explore the Dashboard and this new feature by following this link.
​
📚 Read more about the announcement here.

Segments will be included at no additional cost in some of the pricing plans. Check our pricing page or contact your Customer Success Manager to learn more.

We’re introducing new Android policy-level configurations powered by the latest Android Management API (AMAPI) updates.

These enhancements provide administrators with greater control over connectivity and system update enforcement on company-owned devices running Android 15 and above.

🔐 Control User-Initiated eSIM Additions

Policy: userInitiatedAddEsimSettings

This setting allows IT administrators to define whether end users can add eSIM profiles on corporate-owned devices.

Key highlights:

• 🎯 Enables or restricts user-initiated eSIM additions.
• 🏢 Applies to company-owned devices only.
• 🛡️ Prevents unauthorized eSIM configurations.

This ensures tighter governance over mobile connectivity and reduces the risk of unapproved carrier profiles being installed.

👉🏻 Youcan learn more about userInitiatedAddEsimSettings by following this link.

⏱️ Enforce System Update Compliance

Policy: allowedDaysWithoutUpdate

Part of the System Update configuration object in AMAPI, this setting enforces update compliance policies across managed devices.

Key highlights:

• 📌 Defines the maximum number of consecutive days a device may go without installing a system update.
• 🔢 Accepts integer values greater than zero.
• ⚠️ Flags devices as non-compliant if the threshold is exceeded.

This prevents devices from indefinitely postponing critical OS and security patches, helping maintain operational integrity and network security.

👉🏻 Youcan learn more about allowedDaysWithoutUpdate by following this link.

🔎 Why This Matters

With these new controls, organizations gain fine-grained governance over both device connectivity and update compliance, strengthening security posture while maintaining centralized policy enforcement.

We’re thrilled to unveil a completely redesigned Dashboard — built for clarity, focus, and ultimate usability!
​
✨ What’s new?
We’ve reimagined the layout to make your workflow smoother than ever:

• App Distribution – Manage, publish, and track your apps effortlessly.
• Device Management – Control devices, policies, and enrollments with a clear, dedicated view.
• Inventory – Quickly see all your assets in one intuitive space.

This new structure ensures:

• 🧭 User-friendly navigation – everything is organized exactly where it should be.
• 🎯 Role-focused access – administrators only see what matters for their subscription plan.
• ⚡ Intuitive workflows – spend less time searching and more time managing.
  ​

The new Applivery Dashboard is more than just a redesign — it’s a smarter, faster, and cleaner way to manage your apps, devices, and inventory.
​
💡 Ready to explore? Stay tuned — you’ll be able to experience the difference in the coming days.

We’re happy to announce that Windows Agent v1 is now ready! This first release includes core functionality to help you manage Windows devices more efficiently.

What’s included in v1:

🧩 Supported architectures: x64 (64-bit) and x86 (32-bit). ARM support is coming soon.

📦 App installation and removal: Manage both forced installs and available apps, with support for App Distribution.

🗂️ Curated app catalog: Access a curated catalog of applications.

📁 Installer support: Deploy applications using both .msi and .exe files.

⚙️ Script execution and reporting: Run scripts as one-time, recurring, or on-demand actions, with execution reporting included.

We’re excited to introduce a new feature that makes deploying Custom Android Apps easier than ever!

What’s New

🚀 Deploy Apps from App Distribution:

Users can now deploy applications directly from the App Distribution section to Fully Managed Android devices.

🛠️ Assign a Deployed App Build at Policy Level:

To deploy an app using a policy:

1. Go to Policies and select the policy where you want to deploy a Custom App.
2. Navigate to the Apps section.
3. Click + Add App.
4. Select the Applivery tab and choose the app and build you want to deploy.

With this update, you can now distribute custom apps to your Fully Managed Android devices, ensuring your users always have the right builds quickly and reliably.