After signing up for Zoho People subscription, you can go ahead to configure SAML authentication for Zoho People by adding it as a non-gallery application in Azure AD. While adding the gallery apps or non-gallery apps to Azure AD, one of the SSO options available is SAML based SSO. With SAML, Azure AD authenticates application by using the user’s Azure AD account. In this article, we will see how to register Zoho People as a non-gallery application in Azure AD and how we can configure SAML authentication for SSO in 3 steps. To configure SAML SSO for a non-gallery application, you need to have an Azure AD Premium subscription. Steps 1: Registering the Zoho People application. Registering Zoho People as a non-gallery application in Azure AD. Go to Azure AD > Enterprise Application > Click ‘+ New Application’. Under add an application, select a Non-gallery application.  Provide a name to the application. Here, I am providing the name Zoho People – CFT (Org name) and then click ADD. After the application is added, it will show up under the Enterprise Application list. Click on Single Sign-on, it will show up methods to configure SSO, here choose SAML. Step 2: Configuring SAML in Zoho Accounts. Before configuring SAML in Azure AD, you will need to configure SAML into Zoho accounts. Sign in to Zoho People account as an administrator and then go to My Account. You will be redirected to the Zoho Accounts page. Click SAML Authentication under Settings and then click Setup Now.  Provide the required details. You can get all the above details from Azure AD. Go to the application you registered in Step 1 and then click on Single Sign-on.Sign-In URL & Logout URL: Both the URL you can keep it as Sign-In URL (shown in below screenshot) or else leave the Logout URL blank.Note – I tried Logout URL from SAML configuration (Azure AD), but it is giving an error while logging out from Zoho People and hence keeping the Logout URL blank. Public Key: Download the certificate (Base 64) and upload it. Zoho Service: Select “People”. Algorithm: RSA (by default RSA is selected). Change password URL: This will be the same as Sign-in URL. Click Configure, it will ask to verify yourself (enter password) and then click configure. Once SAML is configured in Zoho Account, you will see the Download Metadata tab. Download Metadata which will need to be uploaded in Azure AD. Step 3: Configuring SAML in Azure AD. SAML authentication is configured on Zoho Account. Now, you will need to upload the metadata which we downloaded in Step 2. Go to Azure AD > Enterprise Application > Zoho People -CFT > Sign Sign-on. Click on the Upload metadata file. Upload the metadata file downloaded from Step 2. Once uploaded, it will open a Basic SAML configuration. You will see that the Identifier (Entity ID) and Reply URL will be populated automatically. Change the Identifier (Entity ID) from Zoho.com to Zoho.in, because we can see the URL for login in to Zoho People is zoho.in. Instead of changing Zoho.com, you can also add Zoho.in and make it as default. Click Save. Once the SAML configuration is done, go to Users and Groups and add users. After adding users in the App, the application will appear on the Access Panel for assigned users. Test the SSO with the application. Accessing Zoho Application: Directly through Zoho People URL – https://people.zoho.in/ From the Access Panel (myapps.microsoft.com), users can find the Zoho People – CFT application. From office.com – Users can fins Zoho People-CFT under all apps.  This article will help you configuring SAML authentication for Single Sign-on. If you are facing any issues with SSO, you can just configure SAML authentication for application and the end-users will be able to leverage SSO for the third-party applications.  

Most of the organization are using the built-in integration between Dynamics 365 and SharePoint, which allows the organization to manage and store documents in SharePoint. Microsoft has expanded the document management capabilities for Dynamics 365 with the built-in integration of Dynamics 365 with OneDrive for Business. With this integration, users can manage the documents for the D365 CE entities from their OneDrive for Business. In this article, we are going to see how to enable Dynamics 365 integration with OneDrive for Business. IT Considerations: No additional software required. You need to have the System Administration role in Dynamics 365 to enable OneDrive for Business integration with D365. Users must have a SharePoint Online license. Enabling D365 integration with OneDrive for Business: Go to Settings > Document Management > Enable OneDrive for Business. Tick on Enable OneDrive for Business and click OK. After enabling OneDrive for Business, you can see OneDrive for Business Folder Settings, in which you can define the folder which will be used for storing the Dynamics 365 documents in your OneDrive for Business. You can see the default folder as /CRM. Go to Dynamics 365 records > Related > Documents. In the Document Location, you will see two folders appeared. OneDrive – From here you can save the document in OneDrive CRM Shared with me  – Files shared with you for the associated record will be shown here. Using OneDrive for Business for Dynamics 365 Entities: Once you are in the Document Location of a record, you can create or upload the document in OneDrive. You will need to first select OneDrive in Document Location. In this case, I am uploading a document to OneDrive for an Opportunity. When I select All locations, I will be able to see all the documents associated with this record. The above-uploaded document has now been associated with this Opportunity. Here is how the folder gets created in your OneDrive for Business. The folder structure will be like CRM > Opportunity > Record. Now, let’s see if the other user can access the OneDrive document I uploaded for the record. I went to the same record and selected All locations. So, the user is only able to see the files on SharePoint. Let’s try to share this file with the user and see if it is accessible after sharing. When the file was shared with other users, the document is now visible under Shared with me a folder or under All locations in the D365 record. You can check the source; it says Shared with Me. This is how we can integrate Dynamics 365 CE with OneDrive for Business and can associate their documents with D365 for Customer Engagement records which any other individual will not be able to see unless the file is shared.

If your organization is using Zoho People and Office 365, you will find this article very useful. In this article we are going to synchronize users between two applications, we will link Zoho people with Office 365 and can log in to Zoho People using Office 365 password instead of having a separate password for both the applications. IT Considerations: Zoho People subscription is required. Office 365 subscription is required. This article basically applies if you have a new Zoho people system and none of the users is added yet. If the users are already added in Zoho, there is a password created already for accessing Zoho People. Domain DNS Zone credential is required for the domain verification process. Step 1: Get the Zoho People App. Sign in to your Office 365 account (portal.office.com). Click on All Apps and click the Add-In button. Search for the Zoho People App and click on “GET IT NOW” and then click on Continue (check below screenshot). Once the above process is followed, you will be asked to log in and then provide permission to the app. Once you accept, you will be able to access Zoho People. The administrator who installs the Zoho People app for Office 365 will automatically become an admin in Zoho People. After you get the app, it will be shown in the app list on portal.office.com. Step 2: Adding users from Office 365. Once the Zoho People app is enabled for Office 365, you can add your users to the Zoho people account from Office 365 tenant. Note – Only Zoho people admin can sync the users from Office 365 to Zoho. To add users from Office 365 tenant, go to Zoho People, click Settings > Users. Click on sync > Import from Office 365. After that, you will be asked to verify the domain (see below screenshot). To verify the domain, you will need to add either the TXT or CNAME records to the DNS Zone for the domain. DNS Propagation may take some time, depending upon where it is hosted. After some time you can click on the verify button. If the DNS propagation is done, the domain will get verified, if it doesn’t get verified, you will need to wait for the propagation. You can see the verification status in the below screenshot. You will find the Users from Office 365. Select Users from the list to be added to your Zoho People account and Click ‘Import User’. The imported users will be added to the user’s list in Zoho People. Note – When you have synced the users from Office 365, Zoho People will not create a password for those users and you will need to log in with Office 365 credentials. Step 3: User login – For End-users. Once all the user is added to the Zoho People account, the user will be able to login to Zoho. Here are the steps on how to log in. Log in to portal.office.com and click on All Apps (the same process which is shown in step 1). Click the Add-In button and search for the Zoho People app and then click the “GET IT NOW” button. It will now show in the My Apps on the portal.office.com. End-users can directly go to portal.office.com and then click Zoho People to login. If you directly want to log in to Zoho People without going to the above portal, you can go to the URL – https://www.zoho.com/people/login.html Click on Sign In and since we do not have Zoho People password as we synced the users from office 365 and not created it on Zoho People directly, we will need to click on Sign in with Google or other IDPs. After that select Office 365 and sign in using your Office 365 credentials. Since this will become a longer process, it is better to get the Add-In on portal.office.com and go to Zoho People directly. It will be very helpful for the Admins with regards to the User management since the user will be managed from Office 365 itself, which means adding users and a password reset will be done from Office 365 Admin Center. It’s just that whenever a user is added in Office 365 Admin Center, user list needs to be synced once from Zoho People by the admin. This article will also be very helpful for those who are using Office 365 and Zoho people or who are willing to use Zoho People for HR processes. By following the above process, you can log in to Zoho people by using Office 365 credentials and will not have Zoho People credentials separately to remember.

You might be having some requirements for automatically sending Microsoft Forms survey in recurrence like there might be any type of survey form which needs to be sent out to all the employee on a quarterly basis or monthly basis. To achieve that you can use Microsoft Flow, there are four options available currently Automated Flow, Instant Flow, Scheduled Flow, and Business Process Flow. You need to use the Scheduled Flow, as the survey needs to be sent out in recurrence. Let’s see how to do that. Note: You need to have Microsoft Forms Pro because in Microsoft Forms “Send a Survey” action is not available in Flows. Assuming you have already created Survey in Microsoft Forms Pro. Steps 1: Office 365 Group You must have an Office 365 Group, or you can create one, in which you will need to add all the users to whom you want to send out the survey. Go to Microsoft 365 Admin Center > Groups. Create an Office 365 Group. Add members. Step 2: Creating a new Flow As it will be a scheduled survey, you will need to create a scheduled Flow. Click Create. Select Scheduled Flow. Provide the required details and click Create. Automatically this Recurrence tab will be there, where you can make changes in the frequency in which this survey will be sent. You can also specify the advanced options, where you can select the Time zone and start time. Click on +New step and then in Choose an action search for “Office 365 Group”. This is required as the Flow will require the list of addresses on which the survey will be sent. After selecting Office 365 Groups, choose Actions “List Group Members” and then select the Office 365 Group which you created earlier in Step 1. Click on New Step again and search for Microsoft Forms Pro and then choose Action “Send a Survey”. You will need to provide the following details (see screenshot). To: When you click on ‘To’ field, you will get a list of Dynamics Content from which you will have to choose “Mail”. After selecting Mail in the ‘To’ field it will look something like this, again you will need to click on Send a Survey. It asked for the ‘To’ filed again, click on the To field and from Dynamic Content, select ‘Mail’. Survey: You will need to select the Survey which you created in Microsoft Forms Pro. Email Template: There are already few default templates provide, you can choose from that. For now, “Enter Custom Value” shouldn’t be selected. The Flow is completed now, and you can go ahead and Save the flow and test if it is working as expected. I hope this article helps you in sending a Microsoft Forms survey automatically to all the people added in the Office 365 Group on a frequency which you set in the Flow. Thanks!

Modern authentication in Exchange Online enables authentication features like multi-factor authentication (MFA). Modern Authentication is by default enabled in Exchange Online and Outlook 2013 or later supports Modern authentication. I got this issue from one of my clients that the users are unable to login to Outlook after they enforce Multi-Factor Authentications for the users and as the users were using Office 2016, I haven’t thought of checking the modern authentication and it is already enabled in Outlook 2013 or later. But then it might be the possibility that somehow, they have disabled it. Of course, they were able to login to Outlook mobile as this will always use modern authentications and it doesn’t depend whether you have disabled modern authentication for Exchange Online. There was a workaround to create an App password to login but then why not modern authentication. So, let’s see how I enabled modern authentication through PowerShell. Connect to Exchange Online PowerShell. Set-ExecutionPolicy RemoteSigned $UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection Import-PSSession $Session -DisableNameChecking 2. Run the following command to enable Modern Authentication connection to Exchange Online by Outlook 2013 or later clients. Set-OrganizationConfig -OAuth2ClientProfileEnabled $true 3. Some organizations might have the requirement to disable modern authentication connection to Exchange Online by Outlook 2013 or later clients. Run the following command to disable the same. Set-OrganizationConfig -OAuth2ClientProfileEnabled $false 4. To verify that the change was successful. Get-OrganizationConfig | Format-Table Name,OAuth* -Auto I hope the above steps will be able to resolve the issues whenever the user is unable to login to Outlook client with Multi-Factor Authentication.

Public Folders in Office 365 are designed for shared access and provide an effective way to collaborate in your Organization. It can be accessed by multiple users depending upon the permission given from the Exchange Admin Center. Public Folder is available on Outlook on the web, Outlook 2007 or later and on Outlook for Mac. Note: Before creating a Public Folder from Exchange, you first need to create a public folder mailbox. Public folder mailboxes contain the hierarchy of information and content for public folders. Create a Public Folder Mailbox: From Exchange Admin Center, go to Public folders > Public folder mailboxes > Click Add (+). Creating a Public Folder mailbox through PowerShell. Connect to Exchange Online through PowerShell. Enter the command “New-Mailbox -PublicFolder -Name <Name>”, provide the name of the public folder mailbox in place of As I had already created Public_Folder as a public folder mailbox, if I try to create a new one from the PowerShell, it will be a secondary hierarchy public folder mailbox. Below I had created a new one with the name of “twitter”. Creating a Public Folder: Creating a Public Folder through EAC. Go to Public folders > Public folders (on the right-hand side) Click Add (+) and give a name to the Public folder. Creating a Public folder through PowerShell. Connect to Exchange Online through PowerShell. Enter command “New-PublicFolder -Name twitter”, these commands create a public folder on the parent path. Mail-Enable Public Folder: Once you have created a public folder, you can mail-enabled it which will allow users to post to the public folder by sending an email message. When the public folder is mail-enabled additional settings to become available. For example – Mail delivery options, mail delegation, etc. Using EAC to the mail-enable public folder. Navigate to Public Folder > Public Folders. Select the Public folder for which you want to mail-enable. In the details pane, Mail settings, click Enable. To check other additional settings, select the public folder and click Edit. Mail-Enable Public Folder through PowerShell. Connect to Exchange Online through PowerShell. Enter command “Enable-MailPublicFolder -Identity \twitter” Public Folder Permissions: You can add or remove users who can access the public folder and you can also edit the permission level. Go to EAC > Public Folders > Public Folders. Select the public folder for which you want to provide access to a user and edit the permission level. In the details pane, go to Folder Permissions > Manage. For editing the permissions level, click on the user added and then click edit.

After creating a Public Folder, the default reply address for that Public Folder will be with the initial domain (onmicrosoft.com). To change you default email address please follow below steps. Go to EAC > Public Folders > Public Folders. Select the Public Folder you created, check whether it is mail-enabled (If it is mail-enable, then only you can see the additional settings and email address is assigned). Click Edit. Address you can see for Public Folder (Twitter) is twitter@cloudcfs1.onmicrosoft.com. However, you can add SMTP over here, but that will not be your default reply address. Connect to Exchange Online through Windows PowerShell. Once you are connected, you will need to disable to Email Address Policy. Enter command “Set-MailPublicFolder -Identity “\<foldername>” -EmailAddressPolicyEnabled $False” (Provide you public folder name in place of <foldername>. After disabling Email address policy, you will see that “Make this the reply address” option will appear and hence you can enter the new SMTP address and make this as default reply address. Allow anonymous users to send email to a mail-enables public folder: Any emails sent from anonymous user to the Public Folder you created, will bounce back if this permission is not given. Connect to Exchange Online using PowerShell. Enter command “Add-PublicFolderClientPermission “\FolderName” -AccessRights CreateItems -User Anonymous” (provide your public folder name in place of \FolderName).

Domain verification in Office 365 is a very simple task, you just need to add a custom domain, add the TXT or MX record by provided by your tenant with your domain registrar and then verify it. However, sometime you might face issues verifying a domain and end up getting an error like “We have confirmed that you own <DOMAIN_NAME>, but we cannot add it to this tenant at this time. The domain is already added to a different Office 365 tenant”. When you are unable to verify your domain through Office 365, you can also try adding domain from Azure Active Directory.   Basically, If you already manage a tenant with Azure services or Office 365, you cannot add a custom domain name if it is already verified in another Azure AD tenant. What we can do over here is to use the ForceTakeover option with Azure AD PowerShell. Connect to Microsoft online services. 2. Get the domain list currently associated with your O365 tenant. 3. Add the domain which you want to verify and after adding that domain, you can see the status and it will be in the ‘unverified’ stage. 4. Now, you have to get the DNS TXT record for the domain, you need to add the TXT record in your domain registrar. Verification sometimes might now happen immediately because it takes time for the record to propagate. 5. Add the -ForceTakeover needs to be added to the cmdlet only when .forcing an external admin takeover. This method can be used at last after you have tried each method for verifying your domain but still can’t verify it. 6. Once you run the -ForceTakeover cmdlet, the status of the domain will get verified.

Before getting into details, firstly I would like to talk about Microsoft Teams. If you’re familiar with MS Teams, you know that it is chat and collaboration platform – a place to manage all your conversations, files and important tools in one team workspace. You can access SharePoint, Power Bi and now Dynamics 365 for Customer Engagement right from the Teams app and can collaborate. Microsoft Teams comes with the Office 365 subscription and is present with both web and desktop version as well. Dynamics 365 page can be added as a tab on Microsoft Teams channel they are working on to allow easy access to the customer information. The tab added on MS Teams channel is a fully functional page that means you can edit any records or navigate to related records without leaving the app. You can also use Dynamics 365 Bot for quick updates on records. Before getting started,  enable Microsoft Teams integration feature from Dynamics 365 Customer Engagement: Sign in as a System Administrator. Go to Settings > Administration > System Settings > General. Enable Microsoft Teams integration. Let’s get started: I hope you already have Microsoft Teams App installed on your system. Go to the Teams channel where you want to add a Dynamics 365 page as a tab, add a tab by clicking on the + button. Search for Dynamics 365 App. After clicking on the Dynamics 365 App, you will be asked to select the Organization and the App module. Select the same from the dropdown accordingly and click on SELECT. Search for the entity you want to connect the to this channel and click on SAVE. It is done, you can now edit the record details or navigate to the related records in Dynamics 365 from MS Teams app. Once you complete the above steps, you will see a notification of record is successfully connected (see above image). Any changes done here will be synchronized with the Dynamics 365 for Customer Engagement apps. Once the integration is done, Teams also provides the feature to associate files. Any related documents uploaded in the Files tab in Microsoft Teams will also appear in D365 Customer Engagement apps under Documents for the record. Similarly, any documents added in D365 for Customer Engagement apps will appear in the Files tab on Microsoft Teams.Below images is of Microsoft Teams Files tab: Below image is of D365 for CE app > Documents: In the below images, you can see various locations for documents, this is because I have also enabled SharePoint integration. You can select the specific location or All File to view each file related to this record. As you can see in the below images the files uploaded on Microsoft Teams appears over here. If you want open a record in Dynamics 365 for CE and you are in Microsoft Teams currently, don’t bother to enter the URL. Click the Go to Website icon. Setting up the Dynamics 365 Bot: You can set up the bot feature to interact with Dynamics 365 Apps. You can also use Dynamics 365 bot to look up and make a quick update on any record. For setting up please follow the below steps. You can go to the Chat on the left side of the Teams app, and then select Dynamics 365 for Customer Engagement apps. In the welcome message from Bot, it provides some abilities of the bot. You will need to click on Sign in. Select Org and then Click on NEXT. Enter credential and Sign in. The Dynamics 365 bot setup is complete and some option is already loaded to get started.

Introduction: As you know that SharePoint Online can be used as a document management platform and with the help of Document Id’s you can effectively manage your documents by providing an easy way to track irrespective of their location. Document Id’s are automatically assigned to the documents uploaded on document or record management platform. Before using the Document ID features for our document management system, you must enable it for each site collection in which your documents are located. You must be a Site Collection Administrator for enabling this feature in SPO. Activate, enable and configure Document ID’s: Go to the top-level Site collection > Site Settings. Under Site Collection Administration, click Site collection features. Next to Document ID, click Activate. Activate icon will appear once the feature is activated. Go back to the Site Settings page and under Site Collection Administration, select Document ID settings. You will have to assign a prefix for the Document ID’s and the prefix should be between 4 to 12 characters with no special character. If you want all the documents within the Site Collection, to be assigned with a Document ID with the specified prefix, check the box “Reset all Document ID’s” (See above image). Once this feature is enabled, any new document created or uploaded to any document library in this particular Site Collection received a unique Document ID. Document Id’s can be viewed from the document properties, these are the hyperlinks that you can copy and use it to open a document in Office. Moving and Copying a file with a Document ID: When you move a file in SharePoint Online, Document ID will move with the file. It basically depends on whether the service is enabled or not at the destination site. So, if the service is not enabled at that site then the document will no longer have the Document ID. When a copy of the document is made, a new Document ID is created for the copy and obviously, the service needs to be enabled at the site where you are copying the file.