Microsoft MS-600 Dumps

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.

clientState specifies the value of the clientState property sent by the service in each notification. The maximum length is 128 characters. The client can check that the notification came from the service by comparing the value of the clientState property sent with the subscription with the value of the clientState property received with each notification.

Note: A subscription allows a client app to receive notifications about changes to data in Microsoft Graph.

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.

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.

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.

Graphical user interface, text, application Description automatically generated

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.

An app catalog is a dedicated site collection in a SharePoint web application or SharePoint Online tenancy that hosts document libraries for Office and SharePoint Add-ins. To make Office Add-ins accessible to users within their organization, administrators can upload Office Add-ins manifest files to the app catalog for their organization. When an administrator registers an app catalog as a trusted catalog, users can insert the add-in from the insertion UI in an Office client application.

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.

The distribution of SalesApp must be automatic and require minimal user interaction.

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

There are currently three methods of app integration in Teams: Connectors, Bots, and Tabs. Tabs offer more

extensive integration by allowing you to view entire third-party services within Microsoft Teams.

Graphical user interface Description automatically generated

"graph.microsoft.com" "drive" onedrive

Box 1: root

/root - The root folder for the drive.

Box 2: $select=id,name

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. For example, when retrieving your messages, you might want to select that only the from and subject properties of messages are returned.

References: com/en-us/onedrive/developer/rest-api/concepts/addressing-driveitems

per.microsoft.com/en-us/graph/docs/overview/query_parameters

A client application gains access to a resource server by declaring permission requests. Two types are available:

"Delegated" permissions, which specify scope-based access using delegated authorization from the signed-in resource owner, are presented to the resource at run-time as "scp" claims in the client's access token.

"Application" permissions, which specify role-based access using the client application's credentials/identity, are presented to the resource at run-time as "roles" claims in the client's access token.

In SPFx we will get the user context using the object “context”. We have msGraphClientFactory available in the same object which will take care of generating the Access Token based on the user context.