Hey everyone,
I’m running into a weird issue with the MS Graph API on 21Vianet Cloud. I’m trying to make a hidden email folder, but it’s not working as expected. The API says it’s successful (status 201), yet the folder appears as a regular one instead of hidden.
I’ve checked my permissions, and I definitely have Mail.ReadWrite, so that’s not likely the issue. Strangely, using the exact same API calls on the Global service cloud works perfectly for hidden folders.
Has anyone else experienced this? The documentation indicates that 21Vianet Cloud should support hidden folder creation. Could there be additional settings or steps I need to consider?
Thanks for any insights!
I’ve encountered this exact problem with 21Vianet’s Graph API implementation. Their hidden folder functionality seems to be inconsistent. One workaround I found is to create the folder normally, then immediately send a second PATCH request to set the isHidden property to true. This two-step process often succeeds where a single creation request fails. Additionally, ensure you’re using the correct API version for 21Vianet, as some features lag behind the global cloud. If all else fails, you might need to reach out to 21Vianet support directly, as they sometimes have undocumented quirks in their API behavior.
I’ve dealt with similar quirks on 21Vianet’s platform. One thing that’s worked for me is using the beta endpoint instead of v1.0. It seems to handle hidden folders better.
Also, check your request body. Make sure you’re explicitly setting ‘isHidden’: true in the JSON payload. Sometimes the API ignores implicit settings.
If that doesn’t work, try creating the folder first, then updating its properties in a separate call. It’s not ideal, but it’s a reliable workaround.
Lastly, consider using the Microsoft.Graph SDK if you aren’t already. It sometimes handles these edge cases better than raw HTTP requests.
Hope this helps! Let us know if you find a solution.
hey hazel, ive run into similar issues with 21vianet. their api can be finicky. have u tried using a different endpoint or adjusting the request payload? sometimes tweaking those helps. also, double-check ur auth token - sometimes that causes weird behavior. good luck!