MS-600 Exam Dumps - Building Applications and Solutions with Microsoft 365 Core Services

Graphical user interface, text, application Description automatically generated

Step 1: Create a bot registration..

Step 2: In the HRApp manifest, configure the botId value in the ComposeExtensions section to match the botId value of the bot registration.

Scenario: HRApp must include a messaging extension that enables users to search jobs by job title or job ID.

Step 3: Implement a handler

Graphical user interface, text, application Description automatically generated

Scenario: Implement single sign-on (SSO) and minimize login prompts across browser tabs.

When your application is open in multiple tabs and you first sign in the user on one tab, the user is also signed in on the other tabs without being prompted. MSAL.js caches the ID token for the user in the browser localStorage and will sign the user in to the application on the other open tabs.

By default, MSAL.js uses sessionStorage which does not allow the session to be shared between tabs. To get SSO between tabs, make sure to set the cacheLocation in MSAL.js to localStorage.

To use Microsoft Graph to read and write resources on behalf of a user, your app must get an access token from the Microsoft identity platform and attach the token to requests that it sends to Microsoft Graph.

One common flow used by native and mobile apps and also by some Web apps is the OAuth 2.0 authorization code grant flow.

Scenario: Email the generated invoices to customers on behalf of the current signed-in user. Any emails generated by the system will contain the invoiced.

Use Azure AD to manage identities, authentication, and authorization.

Scenario: ADatum identifies the following technical requirements for the planned E-invoicing capabilities:

• Ensure that all operations performed by E-invoicing against Office 365 are initiated by a user. Require that the user authorize E-invoicing to access the Office 365 data the first time the application attempts to

access Office 365 data on the user’s behalf.

Sending actionable messages via email is supported. You use actionable message cards.

Scenario:

Create an email workflow solution for expense claims. Users will submit their expense claims and the system will email an approval request to their manager.

The expense claims solution must provide managers with claim information and the ability to manage the claim by using Microsoft Outlook, Outlook on the web, or Outlook for iOS and Android.