MS-100

Join this Study Group to prepare for the exam Managing Identity and Services Exam Code MS-100.

This page designed to help you preparing for MS-100 Managing Identity and Services exam. This is equal to referring to MS-100 Exam Dumps.

I have consolidated the important information on each topic and posted in my blog and added the respective links for easy navigation. If you have a question on MS-100 exam topic or if you want add any information, please post your comments on that topic.

Design and Implement Microsoft 365 Services (25-30%)

      Below are the Topics under Design and Implement Microsoft 365 Services

      Manage Domains

      Manage domains

      You should have complete understanding on managing domains in Office 365 which includes planning and configuring domain, Identity and authentication methods. Microsoft highlighted below sub topics under manage domains.

      Add and configure additional domains

      When you sign up of for Office 365, it includes a default domain name like domainname.onmicrosoft.com. Adding a Domain in Office 365 will help you to have your domain name in your email address instead of default domain. You need to prove that you are the owner of your domain.

      To add, login to O365 Admin Portal https://portal.office.com/adminportal/home -> Setup -> Domains -> Add a Domain -> enter your domain name -> Verify the domain by creating a TXT record -> Setup Online Services -> Update the DNS records.

      Tips:

      • To verify the domain, Office 365 will show an option where if domain register under GoDaddy, Office 365 will verify the domain on your behalf or you can create TXT record.
      • If we choose the option to create a TXT record, a TXT record or an MX record can be created to show the proof of domain ownership.
      • If you create a MX record, make sure you are ok to receive emails through Office 365 as your email gateway.

      Configure user identities for new domain name

      You need to Know the below Identity models available.

      Cloud Identity: User Identity management will be only in Office 365 (Azure AD). No On-Premise servers required to manage users. All the objects management done only in Cloud.

      Synchronized Identity: Identities synchronized from on-premises directory to Office 365 (Azure AD) and user management done at On-Premise AD. Passwords can be synched so that users have the same password on-premises and in the cloud. On-Premise and Office 365 will have same identity but Users has to sign in every time when accessing On-Premise and Office 365 application, no single sign on experience.

      Federated Identity: Identities synchronized from on-premises directory to Office 365 (Azure AD) and user management done at On-Premise AD. Identities Synced to Azure AD will be used to enable the Office 365 services. Users will be authenticated in on-premise AD to access a cloud application via Federated Authentication via ADFS for Single Sign On.

      Tips: Authentication method can be changed from Azure AD connect configuration and we can see the current authentication method at Azure AD Portal -> Azure AD Connect

      Configure workloads for new domain name

      When we add and verify the domain, after verification, it will give an option to enable the workloads like Exchange, Skype for Business, Teams, SharePoint\OneDrive & Mobile Device Management for Office 365, we need to plan the services that we are going to be enable and it will show the DNS records that is required for those services which will point to Office 365.

      Tips:

      • Office 365 can register TXT records on your behalf or you can manually create the TXT records required for the enabled services.
      • Based on the workload selection, Office 365 will prompt you to create the below records. Other Office 365 workloads like Planner, Forms do not require a DNS record.

      In addition to the above, we need to know how to enable the services and do the initial configuration for the below Microsoft 365 workloads

      • Windows 10 Enterprise
      • Office 365 (EXO, SPO, OD4B, Teams)
      • Enterprise Mobility + Security

      Design domain name configuration

      Designing Domain Name includes, adding a custom domain (superhybridcloud.com), sub domain (support.superhybridcloud.com) and multiple domains (learnexchangeserver.com, learnHybridCloud.com) to your Office 365 Subscription.

      We can add up to 900 domains in Office 365 domain settings. But you need to verify the proof ownership for each domain.

      Tips:

      • If you are using Cloud Identity, sub domain addition will be automatically verified. But the DNS records required for the enabled services to be created by you.
      • If you have a requirement to add a sub domain, do not setup Microsoft to manage your DNS by creating NS records.
      • If the parent domain is federated identity, sub domains can be added only from the ADFS servers. You need enable the services once the sub domain added from ADFS server.

      PowerShell: New-MsolFederatedDomain -DomainName support.superhybridcloud.com

      Set primary domain name

      If we add multiple domains in Office 365, we have an options to set one domain as Primary Domain.

      To Set the Primary Domain, login to O365 Admin Portal https://portal.office.com/adminportal/home -> Setup -> Domains -> Select the domain -> Set as Default.

      Tips:

      • If we create user objects in Azure AD, the UPN or the email address will be stamped with the default domain name. This is applicable for Cloud Identity only or when the objects created directly in Office 365.
      • Deploying Windows 10 Enterprise and Intune Setup has a prerequisite to validate the primary domain.

      Verify custom domain

      We need to verify the custom domains (in other words, proving that you are the owner of that domain to Microsoft) and create the DNS records for each Office 365 workloads. Custom domain is nothing but the email addresses that you want on the email addresses.

      To Set the Custom Domain, login to O365 Admin Portal https://portal.office.com/adminportal/home -> Setup -> Domains -> Add the domain -> verify the domain by creating the TXT record provided by Microsoft.

      Please post your comment if you want to add any information which can help others in clearing their exam.

      Plan a Microsoft 365 implementation

      This covers preparing the On-Premise Infrastructure for Microsoft 365 workloads

      Plan for Microsoft 365 on-premises Infrastructure

      This is an important topic, make a note that the title says Planning Microsoft 365 for On-Premise Infrastructure. Planning should include

      • Networking
      • Identity
      • Windows 10 enterprise
      • Office 365 Pro Plus
      • Office 365 Workloads like EXO, SPO, OD4BO, Teams
      • Mobile Device Management
      • Information Protection.

      Networking: Before enabling Office 365 Services, you need to do a Network Validation to avoid latencies

      • You are going to allow the users to access the office 365 services. We need to ensure users are having Internet Bandwidth to access the services. To ensure no issues with connectivity and performance issues due to network limitation
      • Check the connectivity from each office, use Ping, TraceRT, PSPING & Telnet command to check the connectivity and network performance
      • Ensure users are connecting to Office 365 egress endpoints on their region. Ping command to respective service urls can help you identify it. For example – Ping Outlook.Office365.com for Exchange Online.
      • Ensure the Network Service Provider has a direct peering relationship with the Microsoft Global Network in close proximity to that location. Also, validate there is no latency because of network hairpin by having Cloud Access Broker solution etc.
      • Validate whether proxy is required for Office 365 services and see the Office 365 traffic can be bypassed from proxy
      • Do a tweak at Client side like TCP Windows Scaling, Idle Time, Maximum Send Size and Selectivity Acknowledgement to increase the client side performance when accessing Office 365 Service.
      • Identity: Planning an Identity is required provide secure access to Office 365 Services. This includes, Synchronizing User accounts to Office 365, Designating Admin Roles, Protecting Global Admin Accounts, enabling MFA to Users, Monitoring Identity Synchronizing Health, licensing, Monitoring Tenant, license and Sign-In Activity logs. We will see in detail under Plan identity and authentication solution

      Windows 10 Enterprise: Deploying Windows 10 Enterprise to endpoints

      To prepare Windows 10 Enterprise, Microsoft recommends to add and verify the domain that your users going to use to access Office 365 service, could be UPN or primary email address domain. User addition to Office 365 & assigning license is optional at this time and install Office 365 Pro Plus.

      Do an in place upgrade for Windows 7 and 8.1 using SCCM and for the new devices use Windows Auto Pilot Deployment.

      Monitor the device health and ensure it is secure by having Windows Defender.

      Office 365 Pro Plus: Office 365 Pro plus deployment can be done either via SCCM or Office Deployment Tool, we need to consider office updates channels and the frequency.

      Deployment can be through SCCM, ODT from Cloud, ODT from local Source or directly from Office Portal.

      Mobile Device Management:

      Mobile device manage is required to secure Organization resources by Using Microsoft Intune.

      1. Planning – Plan how to control mobile devices using MDM & the application management on the managed devices using MAM.

      MDM: When user enroll their device, they are managed devices, and can receive any policies, rules, and settings used by your organization.

      MAM: MAM policies will control the application from a non-managed device by forcing the user enter a PIN to secure the application access by an authorized user.

      1. Prerequisites – Intune Subscription, Office 365 Subscription, Azure AD Premium, MDM Push certificate for IOS are required.
      2. Setup Intune – Check whether the devices are Supported -> Ensure the domain verification completed -> Sign in to Intune -> enable Device Management -> Add Users.
      3. Enroll Devices -> Users have to enroll their devices to make it Intune Managed. Set up enrollment restrictions and policies for users and devices.
      4. Deploy the apps
      5. Create Compliance Policies and Conditional Access Policies like only managed devices can access the office 365 services.

      Tips: Allowing only the Intune managed devices will add additional security to organization’s data.

      Information Protection: Information protection is a set of policies and technologies that define how you transmit, store, and process sensitive information.

      Information Protection Includes Data Loss Prevention, Office 365 Labels and Azure Information Protection labelling and classification, Threat Management Policies, Sharing Policies in SharePoint, Office 365 Secure Score, Office 365 Cloud App Security and PAIM for just-in-time access for task-based activities.

      Plan identity and authentication solution

      Planning Identity: Planning an Identity is required provide secure access to Office 365 Services. This includes, Synchronizing User accounts to Office 365, Designating Admin Roles, Protecting Global Admin Accounts, enabling MFA to Users, Monitoring Identity Synchronizing Health, licensing, Monitoring Tenant, license and Sign-In Activity logs.

      Planning Steps: Consider Security in mind and do the Identity Planning.

      1. Ensure Users are created or Synchronized from On-Premise AD using AD Connect

      Learn How to install and configure AD Connect to Synchronize objects to Azure AD. It can be downloaded from Microsoft Download center.

      1. Verify only the designated administrators are member of Global Admin Role

      Get-AzureADDirectoryRole | where { $_.DisplayName -eq “Company Administrator” } | Get-AzureADDirectoryRoleMember | Ft DisplayName

      1. Enable Multi factor Authentication for users

      We can enable MFA at the user level so that it will prompt MFA whenever an Office 365 is accessed or we can trigger MFA when certain application is accessed by creating Conditional Access Policies.

      1. Identity Synchronization Monitoring using Azure AD Health Agents

      We can download Azure AD Health Agent from Azure AD Portal and Install in AD Connect servers to monitor the health of AD objects Synchronization to Azure.

      1. Enable Group based licensing if planned

      We can automate the license enablement and disablement by assigning the license to a Group. If a user is removed, then the license will be removed. If user is member of many groups with the same license enabled, then the license will be used once.

      Azure AD Portal -> License -> Select the license and Click on Assign to a User or group.

      1. Enable Azure AD Identity Protection provides
      • Get a consolidated view of flagged users and risk events detected using machine learning algorithms
      • Set risk-based Conditional Access policies to automatically protect your users
      • Improve security posture by acting on vulnerabilities

      We can search for Azure AD Identity Protection in Azure Portal and click on Create to configure the Azure AD Identity protection.

      1. Configure Privileged Identity Management to support on-demand assignment of the global administrator role

         

      2. Simply User Sign in by configuring Azure Active Directory Seamless Single Sign-On

      We can continue to federated authentication If we are already using Federation with ADFS authentication,

      1. Dynamic Group Membership Rules for a Group in Azure AD

      You can create a dynamic group for devices or for users, but you can’t create a rule that contains both users and devices.

      You can’t create a device group based on the device owners’ attributes. Device membership rules can only reference device attributes.

      1. Self Service Group Management and Password resets

      Planning Authentication:

      Below are the authentication options Available. Microsoft will focus on Seamless SSO.

      Federation Authentication with ADFS

      Most of the Companies preferred to use federated authentication. When the federation sign in option enabled, the domain used for authentication will be configured as federated domain in Azure AD. Below shows the authentication flow for federation sign-in

      How it works

      To explain the Federation Sign-in flow, when you access any claims aware application that trusts Azure AD as the STS, the application will redirect you to authenticate with Azure AD, Azure AD prompts you to login with the user name option only and when you enter the user name, the domain validated whether it is a federated domain. Since it is a federated domain, you are redirected to On-Premise ADFS infrastructure, (to WAP server if you are in Internet and to ADFS server if you sign-in from Intranet). ADFS prompts you to enter the user name and password passed and it authenticates with Active Directory. On successful authentication with AD, ADFS send a Security token to User that will be send back to Azure AD for successful authentication.

      Note: You need to maintain a ADFS infrastructure to have this federation sign-in option and it is having additional benefits like you use On-Premise MFA server for multifactor authentication.

      Password Hash Synchronization Authentication

      No need to confuse about the Password Synchronization option, we are not directly synchronizing the password from On-Premise to Azure AD. Only the Hash of the Password hash synchronized with Azure AD using Azure AD connect.

      How it works

      When Password Hash Synchronization authentication enabled for the tenant, Hash of the password hash is available in Azure AD after Synchronization. If a user access a Azure Integrated application, user redirected to authenticate with Azure AD, Azure AD prompt the user to enter the credential, both user name and the password will be entered in Azure AD authentication dialogue window and it will be validated against the hash Synced in Azure. If successful, user will be provided security toke to the authenticate the service\application. Switching from one application to other, prompts the user to validate the credential when this sign-in option used.

      Pass-through Authentication

      If we use the Pass-through authentication, user name the password will be gathered in Azure AD but Passwords validated in On-Premise AD. AuthN Agent configured in AD Connect or any member server supports this Pass through Authentication. Below shows the pass-through authentication flow.

      How it works

      When user access any office 365 application, it will redirect the user to Azure AD for authentication, Azure AD prompt the user to enter both the user and password and it will be sent to AuthN agent server in On-Premise using a securing tunnel established when configuring the AuthN agent. AuthN agent component validate the user name and password with Active Directory using a Win32 API call to Active Directory and the successful authentication will be sent back to Azure AD. Azure AD authentication successful and send a security token to access the application, the user will gain access to Application.

      Azure AD Seamless SSO (enabled when choosing PHS or PTA)

      Azure AD Seamless SSO allow users to sign in to services that use Azure AD user accounts without having to type in their passwords, and in many cases their usernames alone required.

      Seamless SSO works with Password Hash Synchronization and Pass-through authentication. For the seamless SSO to work, the machine has to be domain joined and should have access to AD. Machine authenticates with Azure AD using Kerberos token.

      How it works?

      When Seamless SSO enabled and the additional configurations are deployed, a new computer object created in AD that holds 2 SPN for authentication with Azure AD. Let us assume as User access a claims aware application, user will be redirected to Azure AD for authentication, Azure AD instructs the client to do an authentication test to find the client is SSO capable and it will send a unauthorized response and to get a token a token from AD. Client requests a Kerberos token ticket from AD and the same will be send it to Azure AD, Azure AD returns a security token which will be sent to application and the authentication will be successful.

      Tips: To configure a Sign in method, Azure AD Connect -> User Sign-In to select the preferred authentication.

      If Seamless SSO fails, the other enabled option PTA or PHS will be used for authentication and If Seamless SSO configured, it is recommended that you periodically roll over these Kerberos decryption keys – at least once every 30 days.

      Azure AD Domain Join is not required when using Seamless SSO, but Azure AD Domain Join and Seamless SSO can be combined, if combined, Azure AD Domain join takes preference.

      Please add your comments if you want to highlight something.

      Setup Microsoft 365 tenancy and subscription

      If you are already using Windows 10 Enterprise, Office 365 E3 and Enterprise Mobility + Security E3 / E5 then you can skip this as you are already using the M365 workloads.

      This topic is all about setting up the Office 365 tenant and Azure Subscriptions.

      Configure subscription and tenant roles and workload settings

      • Configure subscription and tenant roles includes the process of Sign up for Microsoft 365 Enterprise and managing the Roles for the Microsoft 365 Tenant Roles.
      • Microsoft 365 Enterprise Tenant is nothing but having Windows 10 Enterprise, Office 365 & Enterprise Mobile + Security.
      • You can be an existing customer already having the above M365 workload enabled in different forms. If you are new organization migrating to Office 365, you can approach Microsoft / Partner to subscribe for Microsoft 365 Enterprise tenant.
      • M365 subscription is like Signing up for the E3 or E5 trial and enable the services that is required for your tenant.
      • Tenant Roles management is required where you designate respective users are Global Administrator and others as designated administrator like Exchange Online Admin / SharePoint administrator.
      • M365 workload setting is enabling \ deploying the services like Windows 10 Enterprise, Office 365 (EXO, SPO \ OD4B & Teams) & Enterprise Mobile + Security to end users.

      Below Azure AD Tenant Roles are available and we can designate respective admins for each service associated with the roles. Tips: For existing Office 365 customers, if you are already using Windows 10 Enterprise, Office 365 & Enterprise Mobile + Security then you are M365 customer.

      Evaluate Microsoft 365 for organization

      If you’re new to Microsoft 365 Enterprise or to a specific product or feature, one of the best ways to gain understanding is to build it out yourself

      Reference – https://docs.microsoft.com/en-us/microsoft-365/enterprise/m365-enterprise-test-lab-guides

      Existing customers may already setup those workloads and you know how to setup services.

      Plan and create tenant

      Understand Office 365 and Microsoft 365 enterprise workloads and plan for the services that is required for your organization approach Microsoft to get the subscription.

      • Start by registering the tenant with Office 365 Trial and add other workloads that is under Microsoft 365.
      • Creating Tenant is the same process that you sign up for the Office 365 Trial and Microsoft will assist you on adding the subscription to your tenant.

      Upgrade existing subscriptions to Microsoft 365

      • Customer already using Office 365 like EXO and SPO can approach Microsoft / Partners to upgrade their existing services to Microsoft 365.
      • Approaching Microsoft or Microsoft Partner is the only available option to upgrade existing Office 365 subscription to Microsoft 365.

      Monitor license allocations

      • License will be assigned on the individual account and we have an option to use group based licensing where the assigning the license on a Group will assign the enabled license to all the members of the group.
      • Group can be Security group or an Azure AD Dynamic Group. Dynamic groups run rules against user object attributes to automatically add and remove users from groups
      • Azure AD Audit logs can be used to monitor who changed the license on the Group enabled with license.

      Manage Microsoft 365 subscription and tenant health

      As a Microsoft 365 administrator, you need to know how to monitor and manage service health alerts, creating service requests, view the reports to understand the license / service usage.

      Manage service health alerts

      We can use Office 365 Admin App / Office 365 Management Pack / Office 365 Service Communication API to view the service statues.

      Office 365 Service Health can be viewed from Office 365 Admin Portal -> Health -> Service health.

      Tips: Minimum of User Management Role permission is required to view Service Health Alerts.

      Create & manage service requests

      We can raise a Service request to get assistance from Microsoft support on the issues that users is facin in your organization.

      Tips:

      • Support Requests can be raised from Office 365 Admin Portal -> Support -> New Service Request.
      • Minimum of Service Administrator Permission is required to raise Support Request.

      Create internal service health response plan

      This is an internal process to monitor the announcement of Planned Outages in Office 365 Message Center, respective team has to announce the management and also in coordination with TAM for additional details.

      Office 365 Admin Portal -> Health -> Message Center

      If it is a Service Incident, Team has a raise service request to follow up from Microsoft support on the existing issues.

      Monitor service health

      Office 365 Service Health can be viewed from Office 365 Admin Portal -> Health -> Service health.

      Configure and review reports, including BI, OMS, and Microsoft 365 reporting

      To view the Office 365 Reports

      Office 365 report can be viewed from Office 365 Admin Portal -> Reports -> You can drill down to the available reports for additional information.

      Reports also available in Security and Compliance Portal Protection.office.com -> Reports -> view the available Security and Compliance based reports

      Office 365 reports can be viewed from Power BI content packs (Office 365 Adoption Content Pack).

      OMS – Operation Management Suite / Solution for Office 365 is used to monitor User/ Admin activities and also it helps to detect and investigate unwanted user behavior. We can also configure alerts like if a user deleted more than 100 files an alert can be send to administrator.

      Schedule and review security and compliance reports

      Reports related to security and compliance can be viewed at protection.office.com -> Reports. We can configure \ manage the schedules for these reports.

      Schedule and review usage metrics

      Available Reports can be scheduled and we need to review the data to ensure the usage is allowed. In addition, the usage reports like license, services usage can be viewed from Microsoft 365 usage analytics portal from Power BI. We need to enable this from Microsoft Power BI by a Global Admin account or any other Service Administrator Role like EXO Admin / SPO admin.

      To enable Microsoft 365 usage analytics – Office 365 Admin Portal -> Reports -> Usage -> navigate to Microsoft 365 usage analytics and turn ON the option. -> Login to Power BI portal -> Get Data, then under More ways to create your own content choose Service Content Packs and select Microsoft 365 usage analytics

      Plan migration of users and data

      We need to plan users and data migration options to Microsoft 365. Users migration means migration Skype for Business users to Skype for Business online and Data Migration includes mailbox migration and files migration by setting up a hybrid infrastructure for respective service.

      Identify data to be migrated and method

      We need to understand from where the data is going to get migrated to Microsoft 365. Below are the data migration options available

      If Exchange On-Premise – Administrator can setup Hybrid Exchange infrastructure for seamless mailbox migration to Exchange Online.

      • Mailbox Move Request
      • PST Import Tool

      If SharePoint / OneDrive for Business -> Administrator can move the files to SharePoint online by

      • SharePoint Migration Tool
      • Users can manually move the data once they get access to SharePoint Online site.
      • OneDrive Sync client can be used to move the data

      Identify users and mailboxes to be migrated and method

      User identification is to find which email systems user is using for example, if exchange On-Premise, we can setup Hybrid Exchange Infrastructure and can migrate the mailbox. If it is a Gmail system, we have the option to migrate the email from Gmail to Office 365. We need to identify the existing email system and do a planning with the available data migration options.

      Plan migration of on-premise users and groups

      User migration, in other words Synchronizing the users to Azure AD / Office 365 can be done via Azure AD Connect. In addition, we need plan the identity model that we are going to use and the authentication method to be planned.

      Import PST Files

      We can use the Import service to move email (PST files) from your organization’s servers to Office 365. We can ship the files to Microsoft or can upload the file over internet by creating an Import Job to upload PST to Azure blob storage and can map (Using Mapping File) each PST file to respective user’s Primary or Archive mailbox.

      Navigate to Protection.Office.com -> Data Governance -> Import -> Create a New Import Job to import the PST into a mailbox.

      Design identity strategy

      Evaluate requirements and solution for synchronization

      Directory synchronization is the Identity provisioning choice for enterprise customers moving to Office 365. Directory synchronization allows identities to be managed in the on-premises AD and all updates to that identity are synchronized to Office 365.

      Azure AD connect is solution to Sync the On-Premise Objects to Azure AD.

      Directory preparation covers

      Attribute updates – Know the attributes that are going to Sync to Azure AD. It is recommended to leave the default selection when configuring the Azure AD Connect for Directory Synchronization. You should know how to stop a Sync of on

      Domain controller placement – It is obvious to keep the Directory Sync server on the site which has the DC.

      Determining the permissions required – Azure AD Connect requirement the below accounts

      For Synchronization:

      • AD DS Connector account: used to read/write information to Windows Server Active Directory
      • ADSync service account: used to run the synchronization service and access the SQL database
      • Azure AD Connector account: used to write information to Azure AD

      For Installation and Configuration:

      • Local Administrator Permission
      • AD Enterprise Administrator
      • Azure AD Global Administrator
      • SQL delegation to configure the DB

      Planning for multiforest/directory scenarios – Microsoft recommends to consolidate the multi forest into single forest before migrating o Office 365.

      Capacity planning for Directory Sync – We need a server with decent configuration for directory Synchronization and normal hardware for SQL installation.

      Two-way synchronization – You to understand the write back options available and required for your organization.

      By default, Hybrid exchange will write back below attributes from Azure AD to On-Premise AD.

      Also, AD connect has an option of Group Write Back, Device write back and Password write back options.

      Evaluate requirements and solution for identity management

      Two identity models are available as Cloud Identity & Federated Identity.

      Cloud Identity: Identity will be created directly in Azure AD and Authentication and Authorization will be done at Azure AD only. We can create Identity Objects using PowerShell or from Office 365 Admin Portal.

      Federated Identity: Source of Authority will be in On-Premise AD and the On-Premise AD objects will be Synced to Azure AD using Azure AD Connect to enable the Microsoft 365 services by assigning a license. When a user tries to access Microsoft 365 service, Azure AD redirects the user to get an authentication token from On-Premise AD through web application proxy and ADFS server and with the valid token from On-Premise AD to Azure AD, the services will be allowed for user.

      We need to Plan and understand the requirements for Azure AD connect deployment and ADFS servers

      Evaluate requirements and solution for authentication

      When it comes to Authentication, like Identity methods we have cloud Authentication and Federated Authentication methods.

      Cloud Authentication: Identity will be in On-Premise or Azure AD but the authentication happens at Azure AD.

      Cloud Authentication: Users will be created in Azure AD and the Authentication and Authorization will happen at Azure AD itself.

      Password Hash Sync with Seamless SSO: User management will be in On-Premise and you Synchronize objects and Password Hash to Azure AD.

      Pass through authentication with Seamless SSO: User management will be in On-Premise and you Synchronize objects. Authentication will be done by Azure AD authentication services by running a small agent in On-Premise to validate the User identity with On-Premise AD.

      Federated Authentication:

      On-premises directory objects are synchronized with Office 365 and users accounts are managed on-premises. When a user access an Office 365 services, he will be redirected to On-Premise AD via ADFS servers.

      Below are the options available for planning based on your requirement.

      Plan identity synchronization by using Azure AD Connect

      Design directory synchronization

      Understand your current Infrastructure and Plan for Synchronizing Identities to Azure AD using AD Connect. If you have more than 5 K employees and an On-Premise AD, then go for Azure AD connect with ADFS servers.

      Things like Attribute Filtering, AD Connect Staging Server for High Availability, HA for ADFS and WAP server and the Writeback options are to be considered based on your requirement.

      If you have multi forest environment, then deploy one AD Connect Server and Sync the Object from all the forest and have the settings like below

      Implement directory synchronization with directory services, federation services, and Azure endpoints

      Prerequisites for Implementing Directory Synchronization:

      • Azure AD Subscription
      • Enterprise Admin in On-Premise AD & Global Admin in Azure AD
      • Outbound Connectivity to Azure IP addresses
      • Windows 2008 R2 or later for Password Hash Sync and Password writeback
      • SQL Server Instance
      • Certificate that has the federation service name
      • DNS Record for ADFS federation service name – sts.superhybridcloud.com both for internal and public.
      • Add the federation service name in intranet zone for Windows Integrated Authentication to work for browser application from Intranet.
      • Add the Federated Domain UPN Suffix

      Tips: For the intranet DNS record, ensure that you use A records and not CNAME records. This is required for windows authentication to work correctly from your domain joined machine.

      The minimum requirements for computers running AD FS or Web Application Servers is the following:

      • CPU: Dual core 1.6 GHz or higher
      • MEMORY: 2 GB or higher

      Implementing ADFS / Federated Identity

      • Install the ADFS Server Role
      • Configure the ADFS server Role
        • Certification should match the ADFS Federation Service Name
        • WID / SQL can be used based on your requirement
        • ADFS service account
      • Install and Configure the WAP Proxy
        • Configure the SSL certification
        • Make sure WAP server is able to resolve the ADFS service name – sts.superhybridcloud.com
        • Public DNS record of ADFS service name to be point to WAP server
      • Configure Federation Trust with Office 365
        • Connect to Microsoft Online Service connect-msolservice
        • Set the MSOL ADFS context server Set-MsolADFSContext –Computer ADFSServerName.SuperHybridCloud.Com
        • Convert the domain to Federated Domain – Convert-MsolDomainToFederated –DomainName SuperHybridCloud.com
        • Verify the federation – Get-MsolFederationProperty –DomainName domain_name.com
        • Enable the idpinitatedSignOn Page for further verification – Set-AdfsProperties -EnableIdPInitiatedSignonPage $true

      Manage identity synchronization by using Azure AD Connect

      Monitor Azure AD Connect Health

      Azure AD Connect health monitoring involves the monitoring for Azure AD Connect Sync, On-Premise AD and ADFS.

      Health of the configured services like Sync, ADFS & ADDS be viewed on the Azure AD health monitoring portal.

      Azure AD Connect Health Sync agents on the AD Connect Server to monitor the objects Sync from On-Premise to Azure AD. It will show the results like

      • Duplicate Attribute
      • Data Mismatch
      • Data Validation Failure
      • Large Attribute
      • Federate Domain Change
      • Existing Admin Role Conflict and few others

      Monitoring & Alerting: To get the health alerts or Sync errors as email, configure the notification settings.

      We can navigate to the below path to install the Azure AD Connect Health Agent

      To verify the AD Connect Health Agent status, we can run the below command from administrative PowerShell.

      Test-AzureADConnectHealthConnectivity -Role ADFS | ADDS | Sync

      Go through all the available settings in your environment

      Manage Azure AD Connect synchronization

      Running the Azure AD Connect Configuration wizard helps to manage below task in AD Connect. You need to know what these tasks are for..

      We need to know the Sync Scheduler option to manage the Synchronization Type, Sync Interval etc.

      Below management task can be done based on requirement.

      • Enabling Device Write back: If we want to manage any application on boarded through ADFS by configuring a Relying Party Trues and if we have a requirement to allow the application only from managed devices (Conditional Access), then we can enable Device Write Back.

      Navigate to Azure AD Connect Configuration -> Device Options

      • Enabling Group Write back: enabling this option will write the Office 365 groups back to On-Premise AD and On-Premise Exchange mailbox can see those group in GAL to send and receive emails.

      Navigate to Azure AD Connect Configuration -> Group Writeback

      • Preventing Accidental Deletions: By default, AD Connect will stop the deletion if the count is more than 500. We can get the current configuration using Get-ADSyncExportDeletionThreshold and configure the threshold using Enable-ADSyncExportDeletionThreshold -DeletionThreshold 500
      • Configuring Run Profiles: Run profiles actually do the Synchronization, we need to run profiles involved in the Synchronization
        • Full Import
        • Full Synchronization
        • Delta Import
        • Delta Synchronization
        • Export

      Configure object filters

      Filtering helps to control which objects appear in Azure Active Directory (Azure AD) from your on-premises directory.

      We can select the properties of the connector to change the Group based / Domain based / OU based filters.

      Filtering can be applied based on Group, Domain, OU and Attributes.

      Attribute filtering based on attributes to be planned. Apply inbound filtering from Active Directory to the metaverse, and outbound filtering from the metaverse to Azure AD. Microsoft recommend that you apply inbound filtering because that is the easiest to maintain. You should only use outbound filtering if it’s required to join objects from more than one forest

      Configure password sync

      Azure AD Connect synchronizes a hash, of the hash, of a user’s password from an on-premises Active Directory instance to a cloud-based Azure AD instance.

      To use password hash synchronization

      • Open Azure AD Connect.
      • Configure directory synchronization
      • Enable password hash synchronization.

      We can configure federated SSO and change the authentication method as Cloud authentication if any outage with ADFS infrastructure.

      Implement multi-forest AD Connect scenarios

      If an organization is having multi forest, then they can use Azure AD Connect to Sync the objects from different forest to Azure AD.

      Azure AD Connect installation wizard offers several options to consolidate users who are represented in multiple forests. The goal is that a user is represented only once in Azure AD

      The default configuration in Azure AD Connect sync assumes:

      • Each user has only one enabled account, and the forest where this account is located is used to authenticate the user. This assumption is for password hash sync, pass-through authentication and federation. UserPrincipalName and sourceAnchor/immutableID come from this forest.
      • Each user has only one mailbox.
      • The forest that hosts the mailbox for a user has the best data quality for attributes visible in the Exchange Global Address List (GAL). If there’s no mailbox for the user, any forest can be used to contribute these attribute values.
      • If you have a linked mailbox, there’s also an account in a different forest used for sign-in.

      Tips: Multi forest with Multi AD connect deployment to synchronize the objects to single Azure AD tenant is not supported.

      Manage Azure AD identities

      Plan Azure AD identities

      We have the option to Cloud Identity and Federated Identity when deploying Microsoft 365. Planning Azure AD Identity includes

      • Plan to enable SSO for the cloud applications.
      • You may have federated Identity, see if you can move from Federated Identity to Cloud Identity by implementing Password Hash Sync and Seamless SSO.
      • Plan for Self Service Password Reset when you have cloud identity
      • Plan for On-Premise application authentication via cloud using Application Proxy.
      • Plan for providing access to all the cloud application via Access Panel

      Implement and manage Azure AD self-service password reset

      If we use cloud identity, then we can enable Azure AD Self Service Password Reset so that end users can reset their passwords on their own which helps to reduce the help desk cost.

      To Implement and Manage Azure AD SSPR:

      1. Enable SSPR

      Azure AD Portal -> Azure AD -> Password Reset -> Select All or based on your requirement -> Select the allowed authentication methods

      1. Enabled Password Writeback

      Step 1: On the AD Connect Configuration Wizard -> Configure -> Customize Synchronization Options -> enabled password writeback

      Step 2: Azure Portal -> Azure AD -> Password Reset -> On-Premise Integration -> Enabled Writeback passwords to On-Premise Organization

      Manage access reviews

      Azure AD Access Reviews enable organizations to efficiently manage group memberships, access to enterprise applications, and role assignments. User’s access can be reviewed on a regular basis to make sure only the right people have continued access.

      To Onboard or enable Access Reviews in Azure AD:

      Azure Portal -> All Services -> Search for Access Reviews -> Onboard -> Create -> New Access Review based on your requirement like reviewing an group membership or role membership or an application access -> set the reviewers for the selected option.

      Tips: Azure AD P2 or EMS E5 license required to use this feature.

      Reviewers has the complete the reviews from Azure AD PIM portal. We can manage the reviews from Azure AD PIM Portal

      Manage groups

      Two type of groups Security and Office 365 can be created in Azure AD. To create a Group, Azure Portal -> Azure AD -> Groups -> Create a New Group.

      Group Types: Security and Office 365 can be created in Azure AD

      Security: Used to manage member and computer access to shared resources for a group of users

      Office 365: Provides collaboration opportunities by giving members access to a shared mailbox, calendar, files, SharePoint site. Users from external organization can be member of Office groups.

      Membership type can be specified to Azure AD groups

      Assigned: To have unique permission for the members of the group

      Dynamic User: Uses dynamic group rules to automatically add and remove members based on user attributes.

      Dynamic Device: Uses dynamic group rules to automatically add and remove devices based on device attributes.

      Group Owners will have access to manage the members of the group, if a group owner is not specified, the resource owner (administrator) will have owner permission by default.

      Tips: Groups Management like New Group creation, deletion, adding / removing members, assigning / removing an owner can be done from the Azure AD Portal -> Group.

      Groups either Security group or Dynamic Distribution Group Synchronized from On-Premise AD will be managed from On-Premise AD only.

      Manage Passwords

      Controlling Passwords:

      Organizations using pure Cloud Identity can use the Azure AD Password Protection to restrict the use of users using Global Banned password list or Custom banned password list.

      Organization using Hybrid Identity can use the Azure AD Password Protection agent installed in On-Premise AD to validate Global Banned password list or Custom banned password list usage in On-Premise AD.

      Managing Password Resets:

      Password Reset Policies can be defined for administrator roles and user accounts based on the controls that we want to implement like, Password Complexity, password reset duration etc.

      If SSPR enabled on Hybrid Identity with Password Hash Sync, then set the authentication methods and inform the users to register the method for easier password reset when required.

      Require user to register the password reset option when sign in will force the users to register the method selected by administrator.

      Tips: Azure AD Premium P1 or P2 is required to use Password Protection feature in Hybrid Identity Method.

      To set a custom banned password list, Azure Portal -> Azure AD -> Authentication Methods -> Password Protection -> Create a New Custom list

      Manage product licenses

      Microsoft 365 includes Windows 10 Enterprise, Office 365 Services E3 / E5 and EMS E3 / E5. You need to have those subscriptions. To view the services status on the subscription

      (Get-MsolAccountSku | where {$_.AccountSkuId -eq SuperHybridCloud:ENTERPRISEPACK”}).ServiceStatus

      Manage users

      You know how to manage Users

      Perform bulk user management

      You know how to manage bulk users.

      Manage user roles

      Plan User Roles

      Below are the admin roles available in Azure AD. We can plan to designate these roles to user who manage the Microsoft 365 Services.

      From the Azure AD Portal, navigate to Azure Portal -> Azure AD -> User Settings to manage the below options

      Plan the Enterprise Application settings required for your organization

      Are you going to restrict access to Azure AD Administration Portal?

      Allow \ Restrict users to register an application on their own

      Manage external Collaboration Setting

      Allocate Roles in workloads

      By default, Tenant admin \ Global Admin will have full access to all the Microsoft 365 workloads. In addition, Global Admin can designate other users as administrators on specific Microsoft 365 workloads like EXO and SPO

      Exchange Online

      Below are Roles Available in Exchange Online, we have the RBAC option to define granular permission based on our requirement.

      Skype for Business and Microsoft Teams

      Below are the default admin roles available for Skype for Business and Microsoft Teams

      SharePoint and OneDrive

      SharePoint Online and OneDrive for Business Administrator has only one default admin role – SharePoint Administrator. To give granular control we can assign the particular users are Site Collection Administrators.

      Configure Administrative Accounts:

      We know the below administrative accounts in Azure AD and this can be delegated to respective service administrator.

      Configure MFA to protect those accounts

      Configure Conditional Access Policy to allow the administrator account usage only from Corporate Network

      Configure Access Reviews for the Administrative Role Groups

      Configure Identity Protection for Administrative Accounts

      Use PIM to elevate the permission temporary

      Configure RBAC within Azure AD

      Delegate admin rights

      https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/roles-concept-delegation

      Manage admin roles

      Manage role allocations by using Azure AD

      Open the User properties and assign the above admin roles based on the service that he is managing.

      Plan security and compliance roles for Microsoft 365

      Security and Compliance

      We have the below Default Roles Groups available in Security and Compliance. We can customize this based on our requirement with 29 Roles.

      • Reviewer: Use a limited set of the analysis features in Office 365 Advanced eDiscovery. Members of this group can see only the documents that are assigned to them
      • Records Management: Members of this management role group have permissions to manage and dispose record content.
      • Security Administrator: Members has permission like Security Reader + DLP Compliance Management, Device Management and Audit Logs
      • Organization Management: Members of this management role group have permissions to manage Exchange objects and their properties in the Exchange organization. Members can also delegate role groups and management roles in the organization. This role group shouldn’t be deleted.
      • Supervisory Review: Members can Control policies and permissions for reviewing employee communications.
      • Compliance Administrator: Members can Manage settings for device management, data loss prevention, reports, and preservation.
      • Security Reader: Members can View the Alerts, View DLP Compliance Management, View Device Management and Security Reader
      • eDiscovery Manager: Members can Perform searches and place holds on mailboxes, SharePoint Online sites, and OneDrive for Business locations
      • Service Assurance User: Members can review documents related to security, privacy, and compliance in Office 365 to perform risk and assurance reviews for their own organization
      • Mail Flow Administrator: View Only Recipient Role Assigned

      Manage Authentication

      We will see the available Authentication Methods for Enterprises and how the authentication works in each method.

      Understanding Authentication Methods:

      Below are the authentication options or Sign-In options available for Office 365 / Azure AD.

      • Federation Authentication
      • Password Hash Synchronization Authentication
      • Pass-through Authentication
      • Seamless SSO (enabled when choosing PHS or PTA)

      Federated Authentication

      Most of the Companies preferred to use federated authentication. When the federation sign in option enabled, the domain used for authentication will be configured as federated domain in Azure AD. Below shows the authentication flow for federation sign-in

      How it works

      To explain the Federation Sign-in flow, when you access any claims aware application that trusts Azure AD as the STS, the application will redirect you to authenticate with Azure AD, Azure AD prompts you to login with the user name option only and when you enter the user name, the domain validated whether it is a federated domain. Since it is a federated domain, you are redirected to On-Premise ADFS infrastructure with a Token Request from On-Premise AD, (to WAP server if you are in Internet and to ADFS server if you sign-in from Intranet). ADFS receive the SAML request and prompts you to enter the user name and password passed and it authenticates with Active Directory. On successful authentication with AD, ADFS send a Security token with claims to User that will be send back to Azure AD. Azure AD evaluates the token response and if valid response, Azure AD confirms the successful authentication and user will be allowed to access the application.

      Note: You need to maintain a ADFS infrastructure to have this federation sign-in option and it is having additional benefits like you use On-Premise MFA server for multifactor authentication.

      Password Hash Synchronization Authentication

      No need to confuse about the Password Synchronization option, we are not directly synchronizing the password from On-Premise to Azure AD. Only the Hash of the Password hash synchronized with Azure AD using Azure AD connect.

      How it works

      When Password Hash Synchronization authentication enabled for the tenant, Hash of the password hash is available in Azure AD after Synchronization. If a user access a Azure Integrated application, user redirected to authenticate with Azure AD, Azure AD prompt the user to enter the credential, both user name and the password will be entered in Azure AD authentication dialogue window and it will be validated against the hash Synced in Azure. If successful, user will be provided security token to the authenticate the service\application. Switching from one application to other, prompts the user to validate the credential when this sign-in option used.

      Pass-through Authentication

      If we use the Pass-through authentication, user name the password will be gathered in Azure AD but Passwords validated in On-Premise AD. AuthN Agent configured in AD Connect or any member server supports this Pass through Authentication. Below shows the pass-through authentication flow.

      How it works

      When user access any office 365 application, it will redirect the user to Azure AD for authentication, Azure AD prompt the user to enter both the user and password and it will be sent to AuthN agent server in On-Premise using a securing tunnel established when configuring the AuthN agent. AuthN agent component validate the user name and password with Active Directory using a Win32 API call to Active Directory and the successful authentication will be sent back to Azure AD. Azure AD authentication successful and send a security token to access the application, the user will gain access to Application.

      Seamless Single Sign-On Authentication

      Seamless SSO works with Password Hash Synchronization and Pass-through authentication. For the seamless SSO to work, the machine has to be domain joined and should have access to AD. Machine authenticates with Azure AD using Kerberos token.

      How it works

      When Seamless SSO enabled, new computer object created in AD that holds 2 SPN for authentication with Azure AD. Let us take User access a claims aware application, user will be redirected to Azure AD for authentication, Azure AD instructs the client to do an authentication test to find the client is SSO capable and it will send an unauthorized response and to get a token a token from AD. Client requests a Kerberos token ticket from AD and the same will be send it to Azure AD, Azure AD returns a security token which will sent to application and the authentication will be successful.

      If Seamless SSO fails, the other enabled option PTA or PHS will be used for authentication.

      Design Authentication Method:

      You can choose from below Authentication methods and design your Azure Authentication

      • Cloud Authentication.
      • Federated Authentication
      • Federated Authentication with Password Hash Sync
      • Federated Authentication with Pass-Through Authentication
      • Seamless SSO with Password Hash Sync
      • Seamless SSO with Pass-Through Authentication

      Configure Authentication

      Enterprise Customers will deploy ADFS for authentication and we will see how to configure Microsoft 365 Authentication using ADFS

      ADFS configuration requires

      • Domain Admin Account
      • Publically Trusted Certificate for SSL server authentication
      • ADFS Prerequisites like ADFS Service Name, Service Account, SQL Database etc.
      • DNS A records for ADFS Service Name in Internal and External DNS
      • Domain going to be federated to added and verified in Azure

      Once any of the above authentication method is selected, we have the option to Configure Multi factor Authentication for end users.

      MFA can be enabled at the account level or it can be enabled per application by using Conditional Access.

      Implement Authentication Method

      Below are the 2 options available for configuring authentication for Office 365.

      Configuring Office 365 / Azure AD Authentication via ADFS

      Once the ADFS infrastructure deployed, we need to convert the required domain as federated domain using the below 2 commands

      Set-MsolADFSContext -Computer ADFS_Server_FQDN

      Convert-MsolDomainToFederated –DomainName SuperHybridCloud.com

       

      Above command will convert the domain as federated domain and also it will create a relying party trust for Office 365 services with default claims required for Authentication.

      Configuring Office 365 / Azure AD Authentication via Azure AD Connect

      While configuring the AD Connect, we will have an option to select the sign in option also the ADFS configuration which will convert the domain and create the relying party trust during the Azure AD Connect configuration.

      Make a note, Password Hash Sync and Pass through authentication can be done only from Azure AD Connect.

      Manage Authentication

      To change the authentication method,

      On the AD Connect Configuration Wizard -> Configure -> Configure Sign in Options and select the authentication method required for your organization.

      To view the configured authentication method,

      MFA can be enabled or disabled from the properties of the User Account or via Conditional Access Policy.

      Monitor authentication

      Azure AD Sign-In Logs are available for 30 days for review, we can navigate to Azure AD portal to view the Sign-In logs.

      It requires Azure AD P1 or P2 license to view the Sign-In logs

      Implement Multi-Factor Authentication

      Design an MFA solution

      Azure AD P1, P2, EMS E3 & EMS E5 includes the option to enable Azure Multi factor Authentication. As a Microsoft 365 Enterprise Customer, you need to design MFA authentication to protect your organization data access by authenticated users.

      Design a solution like below

      • Implement Conditional Access to enable MFA for the required applications.
      • If required, set MFA exception is the application is accessed from Compliant / Hybrid Azure AD Joined / Corporate Trusted Location
      • Irrespective of any application force Users with Admin Roles to challenge MFA

      In addition, keep the below questions to design your MFA solution

      • Does your company need to protect privileged accounts with MFA?
      • Does your company need to enable MFA for certain application for compliance reasons?
      • Does your company need to enable MFA for all eligible users of these application or only administrators?
      • Do you need have MFA always enabled or only when the users are logged outside of your corporate network?

      Configure MFA for Apps or Users

      Configured MFA for Apps

      Use Azure AD Conditional Access Policies to enable MFA for Azure On-boarded Application.

      To create a Conditional Access Policy

      Azure Portal -> Azure AD -> Conditional Access -> New CA Policy -> Select the Users -> Select the Application -> review the other settings -> enabled MFA on the Grant section and save

      Configured MFA for Users

      We can enable MFA on the user level so that whenever user access an Office 365 services or Azure AD Integrated Application, user will be prompted for MFA challenge for second factor authentication.

      Azure Portal -> Azure AD -> Users -> Open the Multi-Factor Authentication -> Search for the User -> Enabled MFA

      Administer MFA Users

      Manage MFA Service Settings:

      We can configure below MFA service settings as an administrator for the organization.

      App Passwords: Users can use the app password to sign in to non-browser apps. We have the option to allow or restrict.

      Verification Options:

      If MFA enabled, what are the verification options allowed for users. We can control the options here.

      Remember Multi factor Authentication: If a user passed the MFA validation, it will be a annoying prompt every time they access the service. We can control the option on how long to remember the MFA authentication on that device. By default, this is not enabled.

      Azure Portal -> Azure AD -> Users -> Open the Multi-Factor Authentication -> Service Settings

      Mange User Settings

      If MFA enabled on an account, we have the below options to administer on the account

      Above 3 options are self-explanatory. Please know the available options.

      Report MFA utilization

      MFA activity reports are available for administrator review.

      Navigate to Azure Portal -> Azure AD -> MFA -> Reports -> Activity Reports

      Identify users who have registered for MFA using the PowerShell that follows.

      Get-MsolUser -All | where {$_.StrongAuthenticationMethods -ne $null} | Select-Object -Property UserPrincipalName

      Identify users who have not registered for MFA using the PowerShell that follows.

      Get-MsolUser -All | where {$_.StrongAuthenticationMethods.Count -eq 0} | Select-Object -Property UserPrincipalName

      Configure Application Access

      Configure Application Registration in Azure AD

      Registering the application means that your developers can use Azure AD to authenticate users and request access to user resources such as email, calendar, and documents.

      Registering an application allows any user to do the following:

      • Get an identity for their application that Azure AD recognizes
      • Get one or more secrets/keys that the application can use to authenticate itself to AD
      • Brand the application in the Azure portal with a custom name, logo, etc.
      • Apply Azure AD authorization features to their app, including:
        • Role-Based Access Control (RBAC)
        • Azure Active Directory as oAuth authorization server (secure an API exposed by the application)
      • Declare required permissions necessary for the application to function as expected, including:
        • App permissions (global administrators only). For example: Role membership in another Azure AD application or role membership relative to an Azure Resource, Resource Group, or Subscription
        • Delegated permissions (any user). For example: Azure AD, Sign-in, and Read Profile

      Users can register an application by default. We can control the application registration by users by disabling the App registration option.

      Azure Portal -> Azure AD -> User Settings -> App Registrations -> Select No and Save.

      In addition to the above, we have the below application registration settings to manage for Enterprise Applications. Choose the required option for your organization.

      Configure the app to require user assignment and assign users

      By default, users can access applications without being assigned. However, if the application exposes roles or if you want the application to appear on a user’s access panel, you should require user assignment.

      Suppress user consent

      By default, each user goes through a consent experience to sign in. The consent experience, asking users to grant permissions to an application, can be disconcerting for users who are unfamiliar with making such decisions.

      If we are disabling Application Registration option for end users, only Global Administrator can perform Application Registration. To delegate the permission, we have 2 Azure AD Roles

      Application Administrator: Users in this role can add, manage, and configure enterprise applications, app registrations and manage on-premises like app proxy.

      Application Developer: Users in this role will continue to be able to register app registrations even if the Global Admin has turned off the tenant level switch for “Users can register apps”.

      Configure Azure AD application proxy

      Using Azure AD Application Proxy service helps to integrate the On-Premise application with Azure AD. Refer the below link for additional information.

      https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-proxy-add-on-premises-application

      Publish Enterprise Apps in Azure AD

      Enterprise Applications Published will be available in Access Panel for end users. We can search for application in the Gallery and Publish them for the Users. Below are the default applications published.

      Azure Portal -> Azure AD -> Enterprise Application

      Publish an Enterprise Application

      Click on New Application and Search for the application from the gallery and add it to your organization.

      We can modify the settings of an app like SSO / User provisioning once it is added.

      Implement Access for External users of Microsoft 365 workloads

      Create B2B accounts

      Azure AD B2B collaboration lets you securely share your company’s applications and services with guest users from any other organization, while maintaining control over your own corporate data.

      Administrators can create B2B guest accounts in Azure AD and can send in invitation link for guest users to accept privacy statement.

      Non Administrator users also can B2B accounts by sending an invitation to external user and add them in a Group or share an application to guest users. To make it work, Global Administrator has to enabled self-service management for a group and assign the user as owner of the group and the group be added in the application.

      Conditional Access can be used to control the organization data.

      To create a B2B account

      Azure Portal -> Azure AD -> Users -> New Guest User -> email address and the personal message and click on Send Invite.

      Guest can accept the invitation link and the external user account will be shown as Guest User in Azure AD.

      Create guest accounts

      Guest account creation is same as B2B account creation.

      Design solutions for external access

      We can plan the external access restriction with the below settings.

      Navigate to Azure Portal -> Azure AD -> User Settings -> Manage External Collaboration Settings

      Guest Users Permissions are Limited

      Admins and Users in the guest inviter role can invite

      Members can Invite

      Guest can Invite

      In addition to the above external access settings, we can configure the below collaboration restrictions

      • Identify hybrid requirements
      • Plan connectivity and data flow for each workload
      • Plan for Microsoft 365 workload connectivity
      • Plan migration strategy for workloads

      • Manage Office 365 software downloads
      • Plan for Office 365 apps
      • Plan for Office 365 Pro plus apps updates
      • Plan for Office 365 Pro plus connectivity
      • Plan for Office online
      • Plan Office 365 Pro plus deployment

    8 Responses



    Leave a Reply

    Your email address will not be published. Required fields are marked *