MS-600 Building Applications and Solutions with Microsoft 365 Core Services Questions and Answers

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

Graphical user interface, text, application Description automatically generated

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.

Graphical user interface, text, application Description automatically generated

Box 1: Yes

Using the isolated web parts capability, you can build web parts that securely communicate with APIs secured with Azure AD without exposing the access token to other components on the page or even scripts in the tenant.

When deploying these solutions to the app catalog, all API permission requests are specified as isolated.

Box 2: Yes

Even though on runtime isolated web parts will be loaded inside an iframe pointing to a unique domain, you can communicate with SharePoint REST API, the same way as you would in non-isolated web parts.

Box 3: Yes

If you're upgrading an existing SharePoint Framework project to v1.8.0 and want to use the isolated permissions capability, you can do it, by setting in the config/package-solution.json file, the isDomainIsolated property to true. You should ensure, that your project contains only web parts.

After changing the project to use isolated permissions, you should redeploy your project. This will issue new API permission requests, isolated to your solution, which will need to be approved by the tenant admin.

Graphical user interface, text, application Description automatically generated

Box 1: Office Add-ins

Scenario: SalesApp must be integrated with Microsoft Word and must combine images and text from multiple sources to create a quotation as a DOCX file.

You can use the Office Add-ins platform to build solutions that extend Office applications and interact with content in Office documents.

Box 2: Microsoft Visual Studio

Visual Studio can be used to create Office Add-ins for Excel, Outlook, Word, and PowerPoint. An Office Add-in project gets created as part of a Visual Studio solution and uses HTML, CSS, and JavaScript.

Box 3: Fluent UI

Fluent UI is the upcoming and continually evolving design system for Microsoft 365. Currently, there is an ongoing merge in the process to have one consistent UI Framework across the Microsoft ecosystem.

Here is a quick overview of the steps:

Step 1: Register an application in Azure AD for the backend web service

Register an application (backend-app) in Azure AD to represent the API.

Step 2: Set the App ID URI for the backend service application registration

When the application is created (step 1) select Expose an API and click on Save and continue to create an Application ID URI.

Step 3: Defend the scopes in the backend web service application registration

In the Add a scope page, create a new scope supported by the API. (e.g., Read) then click on Add scope to create the scope. Repeat this step to add all scopes supported by your API.

Step 4: Register an application in Azure AD for E-invoicing.

Step 4.1 Register another application in Azure AD to represent a client application

Step 4.2 Now that you have registered two applications to represent the API and the Developer Console, you need to grant permissions to allow the client-app to call the backend-app.

Scenario:

Secure access to the backend web service by using Azure AD

E-invoicing will have internal logic that will dynamically identify whether the user should be allowed to call the backend API.

Graphical user interface, text Description automatically generated

The AadHttpClient client object is useful for consuming any REST API. You can use it to consume Microsoft Graph or any other third-party (or first-party) REST API.

To consume any REST API using the AadHttpClient client object, create a new instance of the AadHttpClient type by calling the context.aadHttpClientFactory.getClient() method and providing the URI of the target service.

Graphical user interface, text, application, chat or text message Description automatically generated

There are some updates to the Microsoft Teams manifest that require user acceptance to complete:

• A bot was added or removed
• An existing bot's "botId" property changed
• An existing bot's "isNotificationOnly" property changed
• A bot's SupportsCalling, SupportsVideo , and SupportsFiles capability was added
• A messaging extension was added
• A new connector was added
• Properties inside "webApplicationInfo" changed

Get user's manager. Returns the user or organizational contact assigned as the user's manager.

Syntax:

GET /me/manager

GET /users/{id | userPrincipalName}/manager

Only the name of the user's manager should be displayed so we use ?select=displayname

To specify a different set of properties to return than the default set provided by the Graph, use the $select query option. The $select option allows for choosing a subset or superset of the default set returned.

References: https://docs.mic rosoft.com/en-us/graph/api/user-list-manager

https://developer.microsoft.com/en-us/graph/docs/overview/query_parameters

Microsoft Graph Calendars.Read allows the app to read events in user calendars.

For your app to access data in Microsoft Graph, the user or administrator must grant it the correct permissions via a consent process.

Application permissions are used by apps that run without a signed-in user present; for example, apps that run as background services or daemons. Application permissions can only be consented by an administrator.

For the event, group event, group post, message, personal contact, task, task list resource types, you can use the same REST request as getting the resource instance, look for an extension that matches a filter on its id property, and expand the instance with the extension. The response includes most of the resource properties.

Example: GET /users/{Id|userPrincipalName}/events/{Id}/extensions/{extensionId}

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.