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

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.<br />
<br />
Reference: https://docs.microsoft.com/en-us/graph/permissions-reference

<img src="https://examsqa.com/storage/question-images/building-applications-and-solutions-with-microsoft-365-core-services-exam-ms-600_page_8_Im6.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Here is a quick overview of the steps:<br />
<br />
Step 1: Register an application in Azure AD for the backend web service<br />
Register an application (backend-app) in Azure AD to represent the API.<br />
<br />
Step 2: Set the App ID URI for the backend service application registration<br />
When the application is created (step 1) select Expose an API and click on Save and continue to create an Application ID URI.<br />
<br />
Step 3: Defend the scopes in the backend web service application registration<br />
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.<br />
<br />
Step 4: Register an application in Azure AD for E-invoicing.<br />
<br />
Step 4.1 Register another application in Azure AD to represent a client application<br />
<br />
Step 4.2 Now that you have registered two applications to represent the API and the Developer<br />
Console, you need to grant permissions to allow the client-app to call the backend-app.<br />
<br />
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.<br />
<br />
Reference: https://docs.microsoft.com/en-us/azure/api-management/api-management-howto- protect-backend-with-aad

Scenario: Implement single sign-on (SSO) and minimize login prompts across browser tabs.<br />
<br />
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.<br />
<br />
Reference: https://docs.microsoft.com/bs-latn-ba/Azure/active-directory/develop/msal-js-sso

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.<br />
<br />
Note: A subscription allows a client app to receive notifications about changes to data in Microsoft Graph.<br />
<br />
Reference: https://docs.microsoft.com/en-us/graph/api/resources/subscription

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.<br />
<br />
Reference: https://docs.microsoft.com/en-us/graph/auth-v2-user