Microsoft 365

What is it? PIM is basically a service in Azure Active Directory (Azure AD) that enables you to manage, control, and monitor access to important resources of an organization including resources in Azure AD, Azure, and other Microsoft Online Services such as Microsoft 365 or Microsoft Intune. It provides a way to enable on-demand time-limited access for administrative tasks. Why use PIM? An organization always needs to monitor and protect the use of elevated permissions to mitigate the risks of excessive, unnecessary, or misused access permissions on resources that can leak some sensitive information or fall into the wrong hands. We can use PIM in this case and give users just-in-time privileged access to Azure and Azure AD resources and can oversee what those users are doing with their privileged access. Let's try deploying PIM and see how it works for a user. Before deploying, we need to plan what and how are we going to give access to resources and to whom. There are 4 ...

 Team Site: A team site can be created for teams to work on a project and share information with teammates. The team site will associate with a Microsoft 365 group which makes it easier for teammates to collaborate amongst each other. We will create a new team site named SPOLab. You can follow the instructions below for the same: Go to admin.microsoft.com  which should redirect to the Home Page of the M365 Admin Center. If not shown already, click on Show all tab under Admin centers to see all the admin centers and select SharePoint to go to the SharePoint Admin Center. In the SharePoint admin center, expand Sites , and select Active sites . Select +Create from the menu in the middle pane. Select Team site in the new window. Fill out the following site information and select Finish to complete the site creation: Site Name: SPOLabs Group Owner: Select yourself As you see, other information is prefilled and can be edited, if needed, we'll keep it as is for this lab Once yo...

  Prerequisites: Exchange Server 2016 installed Active Directory (AD) associated with the server   There are two ways a mailbox can be created for a user and we’ll discuss both, by using the Exchange Admin Center (EAC) and using the Exchange Management Shell. I already have installed the Exchange Server 2013 on my Windows 2019 server. Creating a UserMailbox through Exchange Management Shell Open EMS on-premises server and the command we would use to create a mailbox would be as follows: New-Mailbox -UserPrincipalName jchris@domain.com -Alias jchris -Database "Mailbox Database 1375581980" -Name JasonChris -OrganizationalUnit "beyounick.local/Synced OU/Users" -Password (ConvertTo-Securestring "Password@123" -AsPlainText -Force) -FirstName Jason -LastName Chris -DisplayName "Jason Chris" The above command would create a mailbox with the UPN jchris@domain.com on the Database Mailbox Database 1375581980 in the OU beyounick.local/Synced ...

Prerequisite: Exchange Server installed Active Directory associated with the server Hoping we have the Exchange Server installed, we would check a few basic configurations. For my test environment, I have Exchange Server 2013 installed on my Windows Server 2019. To access the EAC, we would go to http://localhost/ecp on a browser (http is used here explicitly as if it would try to fetch through https, it would give us certificate error): Once signed in with Admin credentials navigate to Servers > Virtual Directories and note the ECP, OWA internal URLs; we can use them instead of localhost/ecp etc. from within your internal network. Notice, there’s no External URL in this case, but in a production environment, the External URL will be the one user use from the internet to log into their on-premise mailbox. To setup Hybrid environment, go to the Hybrid section in Office365 tab and click Configure: You’ll see the welcome screen once the Hybrid Configuration Wizard (HCW) ...