To add a disclaimer to all Teams meeting invites, you can use the Exchange admin center to create a mail flow rule that applies the disclaimer to meeting requests. Here are the steps to follow:
* Sign in to the Exchange admin center with your Microsoft 365 username and password1.
* In the left navigation, go to Mail flow > Rules.
* Click Add (+) and then select Create a new rule.
* In the New rule pane, enter a name for the rule, such as "Meeting disclaimer".
* Under Apply this rule if, select A message header includes any of these words.
* In the Specify header name box, enter X-MS-Exchange-Calendar-Meeting-Request. This is a special header that identifies meeting requests2.
* In the Specify words or phrases box, enter True. This means that the rule will apply to any message that has the header set to True.
* Click Add and then OK.
* Under Do the following, select Append the disclaimer.
* In the Specify disclaimer text box, enter the disclaimer text that you want to add to the meeting invites, such as:
Disclaimer: This meeting may be recorded for quality and training purposes.
* Click Enter text and then OK.
* Under Choose a mode for this rule, select Enforce.
* Click Save.
Now, when you or anyone in your organization schedules a Teams meeting, the disclaimer will be added to the meeting invites automatically.

Explanation:

Reference:
https://docs.microsoft.com/en-us/microsoft-365/compliance/retention-policies-teams?view=o365-worldwide
https://docs.microsoft.com/en-us/microsoft-365/compliance/retention-policies-sharepoint?view=o365- worldwide
Topic 2, Contoso, Ltd
Case study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirement, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Overview
Contoso, Ltd. is a pharmaceutical company that has 3,000 users in offices across North America.
Existing Environment
Active Directory
The network contains an on-premises Active Directory domain. All user accounts are in departmental organizational units (OUs).
Microsoft Office 365
All users are assigned a Microsoft Office 365 E5 license and are enabled for the following services:
* Microsoft Yammer
* Microsoft Exchange Online
* Microsoft SharePoint Online
* Microsoft OneDrive for Business
* Azure Active Directory (Azure AD)
* Azure AD
* dynamic group membership
Microsoft Skype for Business
Contoso has an on-premises deployment of Microsoft Skype for Business Server 2015. All the latest cumulative updates are installed on all the servers. The following services are used in Skype for Business Server 2015:
* Meetings
* PSTN calling
* Instant messaging (IM)
* Federation to external companies
Departments
Contoso has the following departments:
* IT
* Sales
* Human resources (HR)
* Research and deployment (R&D)
All groups are created by using dynamic group membership that use the department attribute.
Requirements
Business goals
Contoso identifies the following business goals:
* Migrate the maximum number of users to Microsoft Teams.
* Minimize administrative effort.
Device requirements
Contoso identifies the following device requirements:
* Replace Skype for Business IP phones with Microsoft Teams phones.
* All Microsoft Teams phones must be set to lock automatically after 60 seconds.
Meeting and Live Event Requirements
Contoso identifies the following meeting and live event requirements:
* Requirement1: Guest users must be able to join live events.
* Requirement2: Guest users must always wait in a meeting lobby.
* Requirement3: Contoso users must always bypass the meeting lobby when they join by using the Microsoft Teams client.
* Requirement4: After the upgrade to Microsoft Teams, all meetings must be scheduled by using Microsoft Teams.
Calling Requirements
Contoso identifies the following calling requirements:
* Migrate all existing auto attendants and response groups to Office 365.
* Minimize the on-premises PSTN infrastructure.
Technical Requirements
Guest users must be prevented from making private calls.
Security Requirements
Contoso has the following security requirements for the Microsoft Teams deployment:
* The number of ports allowed on the company's firewall must be limited.
* Team names must be prevented from containing the name of any products produced by Contoso.
* Users in the R&D group must be prevented from sending chat messages to users in other departments.
* To meet the company's compliance policy, users in the sales department must continue to use on- premises Skype for Business for IM and calling only.
Pilot Project
Contoso begins a pilot project for the upgrade to Microsoft Teams.
You identify the following issues during the pilot project:
* Microsoft Teams users report that they often receive continuous notifications from the Microsoft Teams client for 20 minutes.
* Two pilot users in the HR department report that they are not members of the HR team.

Explanation:

Reference:
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/active-directory/governance/create-access- review.md

Reference:
https://support.microsoft.com/en-us/office/create-a-team-from-an-existing-group-24ec428e-40d7-4a1a-ab87-
29be7d145865

Explanation

Reference:
https://docs.microsoft.com/en-us/microsoftteams/coexistence-chat-calls-presence