Identity and Access Management, Identity Governance

When downloading the JDK (Java Development Kit), one is presented by different types of installers, e.g., MSI installer, or the compressed archive version or the plain Installer version. See screenshot that shows the three types of installers available. Which one you would choose depends on whether you want the JDK for your personal Development environment or for your team/enterprise. See below brief explanations for the type of installer. Note, the screenshot shows the versions available for Windows Operating System. URL to download the JDK , Java SE Development Kit  https://www.oracle.com/java/technologies/downloads/#jdk21-windows (a) If you are an individual developer then choose the second option of "x64 Installer". This is an exe file (for Windows as shown in below screenshot) that launches the installation wizard which is straight forward. (b) However, if you need an installer for your team environment or enterprise then choose the "x64 MSI Installer". This in

Account in Active Directory (AD) and account in Azure AD (AAD) Here AD is being referred to as the on-premise AD and  Azure AD (AAD) is the cloud based Active Directory. Here are two scenarios of user accounts.   The AAD user accounts are called as M365 accounts that are required to access MS services in the cloud, like M365 tenants, Exchange online mailboxes etc. Scenario: You only have Azure AD account, and an Exchange online mailbox. In this scenario how are the credentials synced. There is no syncing. Azure AD account acts as the single identity source for accessing both Azure AD and Exchange Online. The Azure AD account is the authoritative source for your identity and credentials. When you are assigned an Exchange Online mailbox, it is linked to your existing Azure AD account. Your Azure AD credentials (username, password) are used to authenticate and access both  Azure AD and your Exchange Online mailbox. There is no synchronization of credentials happening because the Azure AD