To isolate what is causing this.
- Take a look at this doc on requirements for hybrid to see if something is missing.
- Check this thread to see if you can point issue on your scenario.
- You can also test the API with Graph Explorer to see if it works for delegated permissions and check if it only fails for on prep users.

alternativeSecurityIds is a list of complex type. Which field are you referring to? The fields are documented on the link at the start of this comment.

As per the docs, type is int32 which is an integer between -2147483648 to +2147483647

This can be related to replication within AAD as AAD has an internal distributed architecture. When you create new resources, it takes some short window for the resources to be replicated to all AAD nodes even though you get the resource created and returned in the request. This means the subsequent requests that depend on the new resource like the secret can potentially hit a node that does not have the update yet. You may have to implement some kind of retry to handle this. I will share resources that I can find if this is the case for you.

How persistent is this error on your end? Does this happens for directory audit logs when you query a block of the logs like for signIns?

Could you point to the Graph API documentation for the endpoint you want to call using the SDK?

Include also the exact Graph API endpoint you are calling from the power app

What is the error you get? Provide the full error details without any sensitive info like secrets.

What version of the powershell sdk are you using?

Try accessing the item using remote item property. GET /drives/{remoteItem-driveId}/items/{remoteItem-id}. Some of the items in your recent are not in your default drive.

This actually looks like a problem with Graph Explorer. Try this on postman. Graph explorer does not handled stream responses. On postman, there is an option to send and save.

Have you ensured the requirements for hybrid setup that support Graph API are correct? Please check here Use REST APIs to access mailboxes in Exchange hybrid deployments (preview)

@MalleshJambagi-0725 I have update this answer with the documentation you are looking for.

Could you try again and see how persistent the issue is. Also update the question with endpoint you are calling? I get an expected 204 error

How have you obtained the access token? If you used https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token is the user in the same tenant?