getIntegrationsTeamsLinkAadWithHttpInfo method

Future<Response> getIntegrationsTeamsLinkAadWithHttpInfo()

Microsoft sign-in return leg

Where Microsoft returns the user after sign-in. It resolves the verified directory identity and then re-checks the tenant: the signed-in user's tenant must equal the tenant of the chat the link started from, so a valid Microsoft sign-in from a different organization is refused here rather than accepted. This is the leg Teams has and the other platforms do not, which is why the Teams flow has an extra address. This is one leg of a three-leg flow, and the legs are not interchangeable: a browser is expected to arrive here only from the leg before it. The link URL's state proves the prompt was server-minted and carries the CHAT it started from — it is provenance only, and it never decides which account gets linked. The account identity always comes from the platform's own verified sign-in and a host-bound cookie, so forwarding a link to someone else cannot bind their account, and a session lifted into another browser is refused rather than completed. Each link is single-use, and a deployment without linking configured answers 503.

Note: This method returns the HTTP Response.

Implementation

Future<Response> getIntegrationsTeamsLinkAadWithHttpInfo() async {
  // ignore: prefer_const_declarations
  final path = r'/v1/integrations/teams/link/aad';

  // ignore: prefer_final_locals
  Object? postBody;

  final queryParams = <QueryParam>[];
  final headerParams = <String, String>{};
  final formParams = <String, String>{};

  const contentTypes = <String>[];


  return apiClient.invokeAPI(
    path,
    'GET',
    queryParams,
    postBody,
    headerParams,
    formParams,
    contentTypes.isEmpty ? null : contentTypes.first,
  );
}