Create mobileAppContentFile
Namespace: microsoft.graph
Note: The Microsoft Graph API for Intune requires an active Intune license for the tenant.
Create a new mobileAppContentFile object.
Permissions
One of the following permissions is required to call this API. To learn more, including how to choose permissions, see Permissions.
Permission type | Permissions (from least to most privileged) |
---|---|
Delegated (work or school account) | DeviceManagementApps.ReadWrite.All |
Delegated (personal Microsoft account) | Not supported. |
Application | DeviceManagementApps.ReadWrite.All |
HTTP Request
POST /deviceAppManagement/mobileApps/{mobileAppId}/contentVersions/{mobileAppContentId}/files
Request headers
Header | Value |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Accept | application/json |
Request body
In the request body, supply a JSON representation for the mobileAppContentFile object.
The following table shows the properties that are required when you create the mobileAppContentFile.
Property | Type | Description |
---|---|---|
azureStorageUri | String | The Azure Storage URI. |
isCommitted | Boolean | A value indicating whether the file is committed. |
id | String | The File Id. |
createdDateTime | DateTimeOffset | The time the file was created. |
name | String | the file name. |
size | Int64 | The size of the file prior to encryption. |
sizeEncrypted | Int64 | The size of the file after encryption. |
azureStorageUriExpirationDateTime | DateTimeOffset | The time the Azure storage Uri expires. |
manifest | Binary | The manifest information. |
uploadState | mobileAppContentFileUploadState | The state of the current upload request. Possible values are: success , transientError , error , unknown , azureStorageUriRequestSuccess , azureStorageUriRequestPending , azureStorageUriRequestFailed , azureStorageUriRequestTimedOut , azureStorageUriRenewalSuccess , azureStorageUriRenewalPending , azureStorageUriRenewalFailed , azureStorageUriRenewalTimedOut , commitFileSuccess , commitFilePending , commitFileFailed , commitFileTimedOut . |
Response
If successful, this method returns a 201 Created
response code and a mobileAppContentFile object in the response body.
Example
Request
Here is an example of the request.
POST https://graph.microsoft.com/v1.0/deviceAppManagement/mobileApps/{mobileAppId}/contentVersions/{mobileAppContentId}/files
Content-type: application/json
Content-length: 342
{
"@odata.type": "#microsoft.graph.mobileAppContentFile",
"azureStorageUri": "Azure Storage Uri value",
"isCommitted": true,
"name": "Name value",
"size": 4,
"sizeEncrypted": 13,
"azureStorageUriExpirationDateTime": "2017-01-01T00:00:08.4940464-08:00",
"manifest": "bWFuaWZlc3Q=",
"uploadState": "transientError"
}
Response
Here is an example of the response. Note: The response object shown here may be truncated for brevity. All of the properties will be returned from an actual call.
HTTP/1.1 201 Created
Content-Type: application/json
Content-Length: 450
{
"@odata.type": "#microsoft.graph.mobileAppContentFile",
"azureStorageUri": "Azure Storage Uri value",
"isCommitted": true,
"id": "eab2e29b-e29b-eab2-9be2-b2ea9be2b2ea",
"createdDateTime": "2017-01-01T00:02:43.5775965-08:00",
"name": "Name value",
"size": 4,
"sizeEncrypted": 13,
"azureStorageUriExpirationDateTime": "2017-01-01T00:00:08.4940464-08:00",
"manifest": "bWFuaWZlc3Q=",
"uploadState": "transientError"
}
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for