Which plan includes Send to Intune?

Team. On Pro the build page shows a Team notice instead of the panel.

Who can connect and send?

The Owner or an Admin of the workspace, because a send puts the app in your Intune at once. Everyone in the workspace can see the sends on the build page.

Does AppForShare assign the app to users or devices?

No. AppForShare hands the file to your Intune. Assignment to groups and devices stays in Intune, where you set it as usual.

Is the client secret stored?

Yes, encrypted with Google Cloud KMS like store keys. It is never shown again or returned by any API, CLI or MCP tool. Disconnecting deletes it; apps already in Intune stay there.

Can I send an ad hoc build?

Yes. Intune takes it, but an ad hoc build still installs only on the devices in its provisioning profile. The panel says so.

Do I get an email per send?

No. The build page, appforshare store-upload and the MCP tool intune_status show each send with its status, and every send is a line in the activity feed.

AppForShare Open Integrations

Docs

Send to Microsoft Intune

Send an enterprise or ad hoc signed .ipa, or a signed APK, from AppForShare to your company's Microsoft Intune as a line of business app: a new app, or a new version of one that is already there. You keep assigning it to groups in Intune. Team.

1. Make an app registration in Microsoft Entra

In the Microsoft Entra admin center, open App registrations and make a new registration. Single tenant is fine, and no redirect URI is needed.
In API permissions, add a permission: Microsoft Graph, Application permissions, DeviceManagementApps.ReadWrite.All. Then press Grant admin consent for your tenant.
In Certificates and secrets, make a new client secret and copy its Value (not the Secret ID).
From the overview page, copy the Directory (tenant) ID and the Application (client) ID.

2. Connect it in AppForShare

Dashboard, Integrations, Microsoft Intune, Connect. Paste the Directory (tenant) ID, the Application (client) ID and the client secret Value, then press Save and test. AppForShare signs in with the app registration and reads one app to check the permission. If the test fails, the panel says why in plain words. Test runs the check again later; Change replaces the values; Disconnect deletes the secret.

3. Send to Intune from the build page

Open the build and find Send to Intune. An .ipa goes as an iOS line of business app, an APK as an Android line of business app.
Choose a new app and give it a name in Intune, or a new version of an Intune app. For a new version, pick the app with the same bundle id or package name; another app is refused.
Tick the confirm box and press Send to Intune. AppForShare encrypts the file to Intune's format, uploads it through Microsoft Graph to the storage address Intune gives, and commits it.
One send per build at a time. The panel shows each send as queued, sending, sent or failed, with the result.

What is refused

An .ipa signed for the App Store: it only installs from the App Store or TestFlight. Export with the Enterprise or Ad Hoc method and upload that .ipa.
An .ipa signed with a development profile.
An .ipa whose provisioning profile has expired.
An .aab upload. Intune takes a signed APK: upload the APK you would install on a device.
A build without a readable bundle id or package name, version or build number.

CLI and MCP

appforshare store-upload <id|slug> --to intune --yes [--app <id>] [--name <name>] sends a build; --name names a new app and --app picks an existing one by its id. --to intune --list-apps lists the matching Intune apps. It needs a token of an Owner or Admin. The MCP tool intune_status is read only: it tells your AI coding assistant whether a build can go, the connection status and every send so far. Sending is never done from MCP.

# list the line of business apps in your Intune that match this build
npx appforshare store-upload AbC123 --to intune --list-apps

# send as a new app
npx appforshare store-upload AbC123 --to intune --name "Shop (QA)" --yes

# send as a new version of an existing Intune app (its id from --list-apps)
npx appforshare store-upload AbC123 --to intune --app 0f1e2d3c-4b5a-6978-8796-a5b4c3d2e1f0 --yes

Questions

Which plan includes Send to Intune?: Team. On Pro the build page shows a Team notice instead of the panel.
Who can connect and send?: The Owner or an Admin of the workspace, because a send puts the app in your Intune at once. Everyone in the workspace can see the sends on the build page.
Does AppForShare assign the app to users or devices?: No. AppForShare hands the file to your Intune. Assignment to groups and devices stays in Intune, where you set it as usual.
Is the client secret stored?: Yes, encrypted with Google Cloud KMS like store keys. It is never shown again or returned by any API, CLI or MCP tool. Disconnecting deletes it; apps already in Intune stay there.
Can I send an ad hoc build?: Yes. Intune takes it, but an ad hoc build still installs only on the devices in its provisioning profile. The panel says so.
Do I get an email per send?: No. The build page, appforshare store-upload and the MCP tool intune_status show each send with its status, and every send is a line in the activity feed.

Overview: send to Microsoft Intune. Related: store upload, MCP server.