Question : AcmeShell Inc plans to migrate from On-Premises Exchange to Office . The existing directory has numerous service accounts in your On-Premises Windows Active Directory (AD), stored in separate AD Organizational Units (OU) for user accounts. You need to prevent the service accounts in Windows AD from syncing with Azure AD What should you do?
1. Create an OU filter in the Azure AD Module for Windows PowerShell.
2. Configure directory partitions in miisclient.exe.
4. Create an OU filter in the Azure Management Portal.
Correct Answer : Get Lastest Questions and Answer : Exp: The Microsoft Office Server products listed in the "Applies to" section ships a version of the Forefront Identity Manager 2010 (FIM) product that is used to synchronize user profile information between directory systems and SharePoint. FIM includes a client utility (MIISClient.exe) that can be used to view, monitor and alter the state and progress of the user profile synchronization settings and process.
Question : You manage an Azure Active Directory (AD) tenant you plan to allow users to log in to a third-party application by using their Azure AD credentials. To access the application, users will be prompted for their existing third-party user names and passwords. You need to add the application to Azure AD . Which type of application should you add? 1. Existing Single Sign-On with identity provisioning
2. Password Single Sign-On with identity provisioning
4. Password Single Sign-On without identity provisioning
Correct Answer : Get Lastest Questions and Answer : Explanation: Single sign on: For example, if there is an application that is configured to authenticate users using Active Directory Federation Services 2.0, an administrator can use the "Existing Single Sign-On" Not, because of "By using their Azure AD credentials".
So is password Single Sign on.
Identity: User provisioning enables automated user provisioning and deprovisioning of accounts in third-party SaaS applications from within the Azure Management Portal, using your Windows Server Active Directory or Azure AD identity information.
They will use third-party user-names, so, no Prevising.
First you need to choose between an existing SSO solution or a password-based SSO. As it is a requirement to store the credentials in Azure AD, it has to be a password-based SSO. There is no need for identity provisioning, thus the correct answer is D.
User provisioning enables automated user provisioning and deprovisioning of accounts in third-party SaaS applications from within the Azure Management Portal, using your Windows Server Active Directory or Azure AD identity information. When a user is given permissions in Azure AD for one of these applications, an account can be automatically created (provisioned) in the target SaaS application.
From the scenario - Users will be prompted for the EXISTING 3rd party credentials. No need to provision them then.
Configuring password-based single sign-on enables the users in your organization to be automatically signed in to a third-party SaaS application by Azure AD using the user account information from the third-party SaaS application. When you enable this feature, Azure AD collects and securely stores the user account information and the related password.
Configuring password-based single sign-on enables the users in your organization to be automatically signed in to a third-party SaaS application by Azure AD using the user account information from the third-party SaaS application
oPassword based SSO without identity provisioning - These are applications the Azure admin has added with the single sign-on mode set to 'Password based Single Sign-on'. It is important to realize that all users authenticated to the Azure AD will see these applications. The first time a user clicks one of these apps they will be asked to install a lightweight browser plugin for IE or Chrome. Once they restart the browser the next time they navigate to that app they will be asked to enter the username and password combination for that app. This is then securely stored in Azure AD and linked to their organization account. The next time the user clicks that app they will be automatically signed in with the credentials they provided. Updating credentials in the third party app needs the user to update their Azure AD stored credentials from the context menu on the app tile.
oPassword based SSO with identity provisioning - These are applications the Azure admin has added with the single sign-on mode set to 'Password based Single Sign-on' as well as identity provisioning. The first time a user clicks one of these apps they will be asked to install a lightweight browser plugin for IE or Chrome. Once they restart the browser the next time they will be automatically signed in to the application
Question : You plan to use Password Sync on your DirSync Server with Azure Active Directory {Azure AD) on your company network. You configure the DirSync server and complete an initial synchronization of the users.
Several remote users are unable to log in to Office 365. You discover multiple event log entries for "Event ID 611 Password synchronization failed for domain." You need to resolve the password synchronization issue. Which two actions should you perform? Each correct answer presents part of the solution.
A.Restart Azure AD Sync Service. B. Run the Set-FullPasswordSync Power Shell cmdlet. C. Force a manual synchronization on the DirSync server. D. Add the DirSync service account to the Schema Admins domain group.
A full Password Sync, and a full Directory Sync are two distinct activities. A full password sync will synchronize password hashes for all DirSync'ing users. A full Directory Sync does not trigger a full password sync. By default, the only activity that will trigger a full password sync is completing the Windows Azure Active Directory Sync tool Configuration Wizard.
Note You must have Directory Sync tool version 6438.0003 or greater installed in order to perform the process below.
To trigger a full password sync, perform the following steps:
Open PowerShell, and then type Import-Module DirSync Type Set-FullPasswordSync, and then press Enter Load Services.msc Restart the Forefront Identity Manager Synchronization Service Service. Once this is complete, you should see a series of EventId=656 (Password Sync Requests) and EventId=657 (Password Sync Results) indicating that your full password sync has kicked off.