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.

One of the common tasks to import multiple users in Office 365 is to be able to create multiple users in the most efficient way possible. Here’s a quick guide to doing so using Import multiple users feature in Office 365 Admin Center. Download Template for Importing Users Let’s say you are in the Admin Center using portal.office.com. Under Users, You’ll find a button to Add Multiple Users And the feature lets you download a template with some sample data in case you’re unsure of what to enter. Once downloaded, you’ll get the Excel in your system Now, you’ll see some sample data which you can simply delete to add your actual data. And let’s say, your data looks like this. I’ve added Kuldeep Gupta and Subhash Mahato, 2 users with some info. Import Back into O365 Now, we are set to import this in O365. On the same feature, look for Browser button to import. Click Verify to validate the info entered for any errors. Once verified, you can click Next. On the next step, I’ll assign licenses and proceed by clicking Next. Once the processing is done, users will be added And you’ll see 2 new users in O365 with the selected licenses Hope this was easy! 🙂  

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.

While Creating Any Cloud-Hosted Environment in LCS it Is Necessary to create Azure Connector for which ARM(Azure Resource Manager) configuration is necessary. So this article will help you to create Azure Connector. Steps to follow :- Role assignment at the azure portal For Proper Working of Azure Connector make sure you have mentioned role assignment in your azure portal.Visit the Azure portal with the same credential as that of LCS and visit subscription section. Now select Access Control(IIM) In which click on Add Button and select Add Role Assignment. Now Configure the Add Role Assignment field as follows and save those configurations. Authorize link Now Navigate back to LCS in which Project Settings>>Azure Connectors and make sure to autorize link by clicking authorize button. Create Add option for connector Click on Add Button in Azure Connectors section and add Name, Azure subscription Id ,  and Toggle Configure to Azure Resource Manager(ARM) option to Yes. Click on next and Check for the following page Again Click on next move to the next step Upload Management Certificate Download the management certificate Now Upload Downloaded Certificate in Azure portal as follows And upload the certificate Select Region for Connector Navigate back to previous LCS session and Complete setup By selecting required Azure Region Click on confirm and your Azure connector is created and the screen looks as follows  

Let’s say you need to create a new store with multiple registers on CPOS.   It is now possible to have a retail store with multiple registers each running CPOS and each having their own dedicated hardware.   For example: A store with two registers both running CPOS and both having their own receipt printer, scanner, etc. . Here comes the concept of a shared hardware station for CPOS, It may seem impractical to have multiple registers sharing the same scanner, pin pad, etc but it is actually possible.   You’ll need to install a hardware station per CPOS and then you should be good to go.   Sharing hardware can be handy in scenarios with limited space or lesser sales persons moving around taking the sales and so on and it’s valid for CPOS.   Note: However, for MPOS you need a dedicated hardware.   Please notice that you can’t have multiple hardware stations installed on the same machine. Please do correct me anyone if that has changed 🙂 This can be done absolutely and is perfectly possible. Just deploy a Hardware station on each device and it will work as discussed in the example above.

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.