Try-it button opens a blank window in some concept topics in Microsoft Graph docs

[angelgolfer-ms]

Describe the bug
Try-it button appears in some concept topics in Microsoft Graph docs but opens a blank window, like enable online meeting in Outlook, share or delegate calendar.

To Reproduce
Steps to reproduce the behavior:

1. Open this topic in a browser: https://docs.microsoft.com/en-us/graph/outlook-share-or-delegate-calendar
2. Scroll down to the first REST query example (GET https://graph.microsoft.com/beta/users/AlexW@contoso.OnMicrosoft.com/calendar/calendarPermissions).
3. Click the Try It button.
4. Wait for a minute to verify that nothing is going to be displayed in the right pane in the browser.

Expected behavior
If the snippet tool enables the try-it capability in a concept topic (inserts the ```msgraph-interactive tag) and inserts the try-it button for an example REST request, then clicking the button should open Graph Explorer side-by-side on the right pane in the browser.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Edge
• Version 88.0.705.63 (Official build) (64-bit)

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

AB#8114

[thewahome]

I had a chat offline with @angelgolfer-ms
The work from the team running the try-it experience from the concept docs would simply be to pass an empty list of permissions since the concept pages do not have a permissions block

[thewahome]

The experimental fix to make the permissions optional failed
i.e changing permission: string[]; to permission?: string[]; so that the team does not need to pass a permissions property to the iframe

[thewahome]

There are two types of pages:

1. API pages
2. Concept pages

The technical difference with the pages that's related to this task is that Concept pages do not have a permissions block.
The contract between the docs pages and Graph Explorer as they load the iframe is this:

export interface IInitMessage {
  /** Message type. */
  type: 'init';
  /** The user's locale on Docs. */
  locale: string;
  /** The current Docs theme. */
  theme: 'light' | 'dark' | 'high-contrast';
  /** The text within the Docs code block. */
  code: string;
  /** Data extracted from the permissions table. Will be null if Docs cannot locate the permissions table. */
  permission: string[];
}

The work of the permissions property was historically to help in authentication with the required scopes. We do not require this now since we have the scope consent functionality.

The lack of a permissions block in a Concept page causes a failure in the logic that loads the iframe that houses Graph Explorer. Thus the work here is for the docs team to remove the functionality to get the permissions altogether and pass an empty array into the IInitMessage contract.

Thus this:

		const rootElement = document.getElementById('main') as HTMLDivElement;
		const permissions = getPermissions(rootElement);

		// data to send to postMessage instead of passing via query strings
		const initMessage: DocsMessage = {
			type: 'init',
			locale: msDocs.data.userLocale,
			theme: currentTheme,
			code: '', // this is determined when we know what try it button the user clicked
			permissions
               };

Should change to:

	       const rootElement = document.getElementById('main') as HTMLDivElement;
		// data to send to postMessage instead of passing via query strings
		const initMessage: DocsMessage = {
			type: 'init',
			locale: msDocs.data.userLocale,
			theme: currentTheme,
			code: '', // this is determined when we know what try it button the user clicked
			Permissions: []
               };

[thewahome]

The docs team has agreed to tackle the problem and has created a work-item here. We will close this once they are done.