Others

How to Fix Microsoft Graph API Empty Payload Errors in Power Apps

Amos Gikunda Oct 8, 2026 870 views

Question details

The user needs to resolve a 'BadRequest Empty Payload' error that occurs when trying to create Microsoft 365 users using the Microsoft Graph API within a Power Apps canvas app.

How to Fix Microsoft Graph API Empty Payload Errors in Power Apps

Product: Power Apps and Microsoft Graph API
Device & OS: not provided
Scenario: Creating Microsoft 365 user accounts dynamically by passing JSON payload parameters from a Power Apps canvas app via the Microsoft Graph API.
Observed behavior: The API request fails with an 'Empty Payload. JSON content expected' error message, regardless of the values entered in the third parameter or request body.

Before you start

Ensure you have the necessary administrative privileges in your Microsoft 365 tenant and that your Power Apps environment has the appropriate API permissions configured for Microsoft Graph.

Solution 1Recommended

Format the JSON Request Body and Headers

The most common cause of the Empty Payload error is an improperly formatted HTTP request body or missing Content-Type headers.

When calling the Microsoft Graph API, the system expects a strictly formatted JSON object. If Power Apps passes the data as a plain string, or if the headers do not specify JSON, the API will fail to parse the body and return an empty payload error.

Verify Request Headers

Check your HTTP request action in Power Apps and ensure the 'Content-Type' header is strictly set to 'application/json'.

Construct the JSON Payload

Ensure that the request body is a valid JSON object. You must include all required Microsoft Graph user properties: accountEnabled, displayName, mailNickname, userPrincipalName, and passwordProfile.

Check Data Types

Make sure boolean values (like accountEnabled) are passed as true/false without quotes, and string values are properly enclosed in double quotes within your JSON formatting.

Test the Request

Run the app action again. If formatted correctly, the Graph API will successfully parse the payload and process the user creation request.

Format the JSON Request Body and Headers

Required Fields: Missing any mandatory user profile fields can also result in standard bad request errors. Ensure your passwordProfile object contains the nested 'password' attribute.

Solution 2

Seek Assistance from the Power Apps Community

If your syntax is perfectly valid but the error persists, there may be a platform-specific glitch or connector limitation.

Free Microsoft Office alternative

Looking for a Lightweight Alternative for Everyday Office Tasks?

While resolving complex API integrations in Power Apps, you might also need a reliable, fast, and free office suite to document your code, track API endpoints, and manage project data. WPS Office provides an excellent environment for creating comprehensive documentation.

1. Download the Installer: Visit the official WPS Office website and click 'Download WPS Office Free'.
2. Install the Software: Run the downloaded executable file and follow the on-screen instructions to complete the installation.
3. Start Documenting: Open WPS Writer or WPS Spreadsheet to begin organizing your Power Apps API documentation and project workflows.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Lightweight installation with extremely fast startup times.Perfect for documenting API workflows and tracking JSON payload structures.Free to use with a familiar, easy-to-navigate tabbed interface.

microsoft office alternative - wps office

Frequently Asked Questions

Why does the Microsoft Graph API return 'Empty Payload' even when I pass variables in Power Apps?

This usually happens if Power Apps evaluates the passed variable as a plain string rather than parsing it into a proper JSON object, or if the 'Content-Type: application/json' header is missing, causing the API to ignore the body content.

What are the required properties to create a user via Microsoft Graph API?

At a minimum, your JSON payload must include accountEnabled (boolean), displayName (string), mailNickname (string), userPrincipalName (string), and a passwordProfile object containing the password.

How can I test my Microsoft Graph API payload outside of Power Apps?

You can use the Microsoft Graph Explorer tool or a REST client like Postman to manually send the exact JSON payload. If the request succeeds there, the issue is likely with how Power Apps is formatting the HTTP request string.

Office Quick Solutions