Vincent Biret

add tenant switch support in the sign-in area

4

**Is your feature request related to a problem? Please describe.** Today if I use the graph explorer to `GET /beta/servicePrincipals`, it will return only the service principals on the main...

improvement : pre-fill payload for requests

3

Putting a part of the conversation I just had with @yinaa a couple of minutes ago. It'd be awesome to save time and to avoid typos during demos to have...

improvement: link to entities in the response

2

Second part of the conversation I just had with @yinaa it'd be awesome to have above or under the response json preview a list of links of the entities in...

**Environment Information** Provide at least: * JRuby version (`jruby -v`) and command line (flags, JRUBY_OPTS, etc) jruby 9.4.0.0-SNAPSHOT (3.1.0) 2022-02-08 3562498c80 OpenJDK 64-Bit Server VM 11.0.14+9 on 11.0.14+9 +jit [linux-x86_64]...

update-user : The OData request is not supported

4

# Repro ```PowerShell connect-graph -Scopes @("User.ReadWrite.All", "MailboxSettings.ReadWrite") update-user -userId $Id -MailboxSettings @{"timeZone"="Eastern Standard Time"} ``` # Error update-user : The OData request is not supported # Intent PATCH https://graph.microsoft.com/beta/users/id/mailboxSettings ```JSON...

DO NOT MERGE: OpenAPI description update with error mapping

1

this PR is a manual preview of the changes from here https://github.com/microsoft/OpenAPI.NET.OData/pull/167 Not meant to be merged, just being used for kiota changes.

related https://github.com/microsoft/kiota-typescript/pull/87 1. query parameter classes should have a get query parameter name method with a switch to map the generated symbol name to the encoded parameter name. 2. the...

According to the [JSON schema spec](https://datatracker.ietf.org/doc/html/draft-fge-json-schema-validation-00#section-5.5.4) ## AnyOf > An instance validates successfully against this keyword if it validates successfully against *at least one schema* defined by this keyword's value....

Actions/Functions request body/response schemas are duplicated

1

Any OData action/function can be bound to multiple "places" resulting in multiple path items being described. The issue is the request body schema for actions and the response for actions...