In effort of moving off of AppCenter and automating the deployment of an IPA to Intune, I'm using a PowerShell script to chunk and commit the file to Intune. This process is successful if it runs locally. But if it runs in Azure pipeline, it will fail to commit. The pipeline has all the permissions necessary for DeviceManagement. Has anyone ran into this type of issue before?
PATCH https://graph.microsoft.com/v1.0/deviceAppManagement/mobileApps/xxxxxxx-xxxxx-xxxxxx-xxxxx
{
"@odata.type": "#microsoft.graph.iosLOBApp",
"committedContentVersion": "109"
}
VERBOSE: Requested HTTP/1.1 PATCH with 85-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
PATCH https://graph.microsoft.com/v1.0/deviceAppManagement/mobileApps/xxxxxxx-xxxxx-xxxxxx-xxxxx
Response status code does not indicate success: 400 (Bad Request)
{
"error": {
"code": "BadRequest",
"message": "{\r\n \u0022_version\u0022: 3,\r\n \u0022Message\u0022: \u0022An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: 9bf24d20-fcf5-420e-be87-a9ec6f66ae1f - Url: https://fef.msua05.manage.microsoft.com/AppLifecycle_2501/StatelessAppMetadataFEService/deviceAppManagement/mobileApps(\u0027332d7929-9120-4e9d-8cda-02f3ad6b1200\u0027)?api-version=2024-10-25\u0022,\r\n \u0022CustomApiErrorPhrase\u0022: \u0022\u0022,\r\n \u0022RetryAfter\u0022: null,\r\n \u0022ErrorSourceService\u0022: \u0022\u0022,\r\n \u0022HttpHeaders\u0022: \u0022{}\u0022\r\n}",
"innerError": {
"date": "2025-02-12T00:57:58",
"request-id": "9bf24d20-fcf5-420e-be87-a9ec6f66ae1f",
"client-request-id": "9bf24d20-fcf5-420e-be87-a9ec6f66ae1f"
}
}
}