Untitled-5

How to use Package deployer tool to deploy packages for dynamics 365

If you are a developer then you must know what is use of package solutions into dynamics. A package solution contains entities, fields, plugins, your application logic code and etc elements. Sometimes we need more than one package to ship to our customers for their functional dependency. Package deployer tool helps to create a single package that can contain multiple packages, master data files, code, and able to contains almost most of the required elements to create a single package on which we can show custom Html to describe details about the package.

 

We can download the Package Deployer using PowerShell from below link

https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/download-tools-nuget

For creating package using visual studio we need package deployer template you can download it from below site

https://marketplace.visualstudio.com/items?itemName=DynamicsCRMPG.MicrosoftDynamicsCRMSDKTemplates

Run the CRMSDKTemplates.vsix to install the template for your visual studio.

After successful installation, create a new project of type CRM Package

In solution we have PkgFolder, Inside it we have:

Content -folder in which we can configure wizard’s html page to show information regarding package and company.

ImportConfig.xml – Configuration file for mapping data files and solutions.

Here we need to place our configdata and record files as well.

Below is the screenshot:

To create the data file use configuration migration tool of CRM SDK.

Update ImportConfig.xml by mentioned your files. Place the solution which you like to ship.

Update Html according to your needs.

Now Create one folder and place all the code which you found inside PackageDeployment tool.

Build the solution and copy PkgFolder and dll of the project and paste into newly created folder which has PackageDeployement files

Run PackageDeployer, add your orgainization credentials and you will get the deployer wizard as below

Untitled-design

How to optimize automation using Azure DevOps

In this blog, we are discussing a feature of DevOps by which we can optimize automation. Manual testing is out fashioned yet it is still important but if we work on big projects we always feel the testing phase should be performed rapidly. Here at moreYeahs we are optimizing automation using DevOps.

We are using selenium to do automation for testing of the dynamics CRM project. Using the .net Unit test project we created test cases. Under the TestClasses, we defined TestMethod which is basically test cases. Test Classes categories type of test. For best practice, we should always have some basic test cases which need to be performed each time we create a new build to do further development.

Before doing all these we need to write test cases that contain test steps. Test Steps describe the execution steps and expected results that are documented against each one of those steps. Each step is marked pass or fail based on the comparison result between the expected and actual outcomes.

Save test case and copy its id.

Now we need to associate this test to our unit project for it we need to place code on the repository. From the test explorer, we need to associate the test as below.

You need to add the ID of the test case created in azure DevOps’s test case.

You got the link of a test case in ID column which directly opens into azure DevOps.

Here we are ready enough to use one of the most useful features of DevOps which provide true automation. Azure Pipelines is a cloud service that you can use to automatically build and test your code project and make it available to other users. It works with just about any language or project type. Azure Pipelines combines continuous integration (CI) and continuous delivery (CD) to constantly and consistently test and build your code and ship it to any target. Azure Pipeline is its self topic which I will cover on the next blog. Here I would like to discuss the pipeline that will automate the test cases.

Before creating a pipeline we need to create a configuration of test plan in Azure DevOps. The configuration is a platform on which the test code will run. Like which OS to use, which browser to use, etc. All these definitions provided in the configuration.

We need to assign a configuration to test suits so suits will use configuration to run its test cases.

Now we are good to use pipeline’s vsTest task add it into a pipeline and configure it below.

Select test plan from the dropdown, select test suits, select test configuration.

check Test mix contains UI test as it is automation we need to check this.

Save and queue the pipeline and run it. you can see real-time logs as tasks are running.

We can get a summary of test cases also we can get logs of fail test cases. All these features going to provide ease in the development process and help develop more effective softwares.

Untitled-7

Installation and Configuration of Omnichannel – Part 2

INSTALLATION AND CONFIGURATION OF OMNICHANNEL IN CRM D365

This is the second part of the Installation and Configuration of Omnichannel for Customer Service in CRM D365.

If you are not getting the Omnichannel for Customer Service App inside Dynamics 365 Administration Center under the Application Tab to go to Part 1.

Let’s continue with the remaining part.

PURCHASE POWER BI LICENSE

You need a Power BI license for Omnichannel. It needs to be assigned to users in order to configure Omnichannel.

If you have a Power BI license and already assigned to users, then skip this part otherwise follow the below steps to get Power BI license.

  1. Go to Microsoft 365 admin center.
  2. Go to Billing Section in the sidebar and click on Purchase services.
  3. Search for power bi. You will get multiple Power BI services. Select Power BI (free). (You can also opt other options for more features).
4. During the check-out process, you’ll be prompted for a credit card in Step 3 of the checkout process.
5. Select the option of Invoice to skip credit card details, fill details and click on Place Order button at the bottom. You will get a confirmation message.
6. Now go to the Admin center and assign this license to a specific user.
PROVIDE DATA ACCESS CONSENT

To allow Omnichannel for Customer Service to read and write data on behalf of users, follow these below steps:

CONFIGURE OMNICHANNEL FOR CUSTOMER SERVICE

Step 1: Select Omnichannel for Customer Service in Dynamics 365 Administration Center under the Application Tab, and click on Manage.

If you have not provided the data access consent then it will ask you to do. Go to Provide Data Access Consent as mentioned in the above section. After that, you will be redirected to Dynamics 365 Administration Center to manage Omnichannel Instance.

Note: As an admin, you can configure Omnichannel on multiple environments (instances). You can view all organization instances where the Omnichannel app has been configured in the Manage Instances view.

 Step 3: Click on Add an org section to set up Omnichannel for the environment. Here you will be asked to select an organization. Select the organization, Check the checkbox for privacy terms and click on purple continue arrow to proceed.

Step 4: Proceed with Setup Chat, SMS and Facebook by selecting the required options to enable it. At last, you will see this screen.

Step 5: Now click on the check button to complete setup on the Summary page.

Now everything will be under setup and it will take time (In my case it took hours, after some time you can close it and reopen or refresh it ). Till then you can have a coffee or go for a walk or do your pending work.

When setup will be completed you can see the below screen with all enabled channels.

In the next blog will be to carry out the Omnichannel configuration within Dynamics 365 for the different channels, which I’ll be going to cover in the next part of this blog.

I hope this will help you to set up the omnichannel inside CRM D365. Please Feel free to ask questions related to it and also post your comments and feedback.
2-2

Installation and Configuration of Omnichannel – Part 1

I am creating a blog series of posts to help people for installation and setup Omnichannel for Customer Service in CRM D365. I hope these might serve as useful blog posts for everyone.

So, let’s begin with the Installation and Configuration of Omnichannel in CRM D365. 

THERE ARE SEVERAL PREREQUISITE ITEMS THAT ARE NECESSARY IN ORDER TO DO THIS, WITH SEVERAL STEPS.
THERE ARE TWO OPTIONS TO SIGN-UP FOR A FREE 30-DAY TRIAL OF CHANNELS:
  • Channels trial through https://trials.dynamics.com/
  • Channels trial through Microsoft 365 admin center (For more info Click Here )

I’ll configure Omnichannel using the first option. You need to install the Omnichannel Hub in order to be able to access it.

Step 1: Get a Dynamics 365 trial instance, to sign up for a trial account Click Here.

If you already have a Dynamics 365 trial instance, then go to Step 2.

Click on Sign Up Here button and then a pop up will appear to choose for partner or Microsoft employee option.

Continue with the signup option.

Fill all the required details to create an account.

When your setup will be completed, you have to select the required options (Also you can select “All of these” options) as you can see in the below screenshot.

Step 2: After Completing the Setup open Dynamics 365 Administration Center. Under the Application Tab look for Omnichannel for Customer Service App.

Oh! Wait… What? I didn’t find that. 

You may be lucky to get the option of Omnichannel for Customer service to configure. If you find that then jump to Installation and Configuration of Omnichannel – Part 2.

Note: Many of us don’t get this option as Microsoft suggests in its documents as you can see in the above screenshot. Even though you will get Omnichannel Administration and Customer App along with Customer Service Hub in Apps as given in the below screenshot.

Umm…Something is not right. Don’t worry, we can solve this issue as well. It is mandatory to follow the below steps to configure it properly.

 Step 3: So, in order to get the Omnichannel option in the Applications Tab, you need to follow below steps:

It will redirect you to another page with confirmation that you have an existing account. Now Click on the Sign-in button to proceed.

Click on Ok, Got it button.

You can see the screen for setting up…

Once setup has completed, Go to Application tab inside Dynamics 365 Administration Center.

Now you can see the Omnichannel for Customer service.

This Blog is getting bigger, so we will continue with the configuration and remaining setup for Omnichannel in the next part of the blog series. Visit Installation and Configuration of Omnichannel – Part 2 for more details.

I hope this blog series will help you to set up the omnichannel inside CRM D365. Please Feel free to ask questions related to it and also post your comments and feedback.
Untitled-9

SharePoint Integration with MS CRM D365 Portal

Today I tried to Set up SharePoint integration in MS CRM Portal. As usual, I selected Enable option in the confirmation window. It will enable the portal to communicate with SharePoint. While the SharePoint integration is being enabled, the portal restarts and will be unavailable for a few minutes and a message will appear when SharePoint integration is enabled.

But when I clicked on the enable option, I got the message asking for Azure AD consent as given in the below image.

To work around this issue, follow these steps:

PRE-REQUISITES:
  • The CRM user needs to be an Office 365 Global Administrator to be able to access the Office 365 Admin center and thus enable the SharePoint integration with MS Portal.
  • The integration between Dynamics CRM and SharePoint should already exist.
BELOW IS THE STEP BY STEP EXPLANATION OF HOW TO ACHIEVE THE INTEGRATION.

Step 1: Go to Microsoft 365 admin center and select Azure active directory.

Step 2: Go to Azure active directory -> Select App Registrations -> Click on Microsoft CRM Portals.

AAD Admin Center

Step 3: Click on API permissions, so will find all the permissions list as you can see in the below image that some permissions are not granted. To remove them click on remove permission option.

Step 4: Click on Add a permission button and then click on SharePoint.

Step 5: Click on the Delegated Permission option and select all the permissions you required.

Step 6: Don’t forget to grant admin consent, it will take some time to enable on API Permission page.

Step 7: It will add the required SharePoint permissions, respectively. You will also be redirected to provide your consent for the changes to be made in the Azure AD application.

If you do not provide your consent:

  • Enabling or disabling the SharePoint integration will not be complete and an error message will display.
  • Your out-of-the-box Azure AD login on the portal will not work.

Step 8: Now go to PowerApps Portal Admin Center and click on Enable option again as we have done in the initial stage.

It will ask for permission as mentioned in step 8. Click on the Accept button. Now a message will appear when SharePoint integration is enabled successfully.

Untitled-2

Migrate SSRS Report from MS2011 TO Dynamics 365

Here we are trying to migrate reports from MS CRM 2011 Onprem to MS CRM D365. This will also help you for below error or if you are migrating reports from older version to newer version.

When trying to compile a FetchXML-based report in Visual Studio 2015 which had been developed in an earlier version of Visual Studio, we were getting the following error:

Building the report, ReportName.rdl, for SQL Server 2008 R2, 2012 or 2014 Reporting Services.


[rsErrorLoadingCodeModule] Error while loading code module: ‘Microsoft.Crm.Reporting.RdlHelper, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.
Details: Could not load file or assembly ‘Microsoft.Crm.Reporting.RdlHelper, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.
[rsCompilerErrorInExpression] The Language expression for the textrun ‘Table0_Details0.Paragraphs[0].TextRuns[0]’ contains an error: [BC30456] ‘Crm’ is not a member of ‘Microsoft’.

PREREQUISITE

I am mentioning this vital step because before proceeding to further steps this needs to be done.

We had already installed the CRM Report Authoring Extension for CRM 2015, but this helper dll was not being picked up by Visual Studio.

We were able to locate the dll on the SSRS Server of our CRM Development environment – in our case it was located here:

C:\Users\freedom\New folder\PFiles\MSCRM\BidsExtensions

but it may be elsewhere for different versions of SQL or CRM. So if you are not able to find it then you can search for Microsoft.Crm.Reporting.RdlHelper in your machine.

NOTE: GO TO FOLDER WHERE WE HAD INSTALLED BIDS EXTENSIONS.

We need to registered it in the GAC (Global Assembly Cache) on these machines. This is done by running the gacutil.exe utility. In some cases, this might be available from a normal command prompt, but we found we had to access it by running the Visual Studio 2015 ‘Developer Command Prompt for VS2015’.

On Windows 10, you can access this from the start menu like this – You need to run the programme as an Administrator, so find the programme and then Right-Click to Run As Administrator:

With the new window open, navigate to the folder where the dll is and run the command gacutil -i Microsoft.Crm.Reporting.RdlHelper.dll

STEPS TO RESOLVE THIS ISSUE:

If you are compiling a report in Visual Studio and it is giving the error above, you might need to point the report to correct version of the RdlHelper.dll

Open the report in Visual Studio. select Report -> Report Properties from the menu. (This option is only available if the report is open and you have selected an element on the report designer/previewer.)

Now go to References Tab and browse to the correct version of the assembly in the BidExtensions folder, even if the RdlHelper is listed, it may be that this is the wrong version…

Earlier its version was 7.0.0.0 so we need to update it to 9.0.0.0 in my case.

In our case it was located here:  C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.Crm.Reporting.RdlHelper\v4.0_9.0.0.0__31bf3856ad364e35

Exact location of helper will depend the version of the helper which you have installed. If you found any existing references (which are not necessary or may be different version of the dll) remove them.

Untitled-design

Microsoft CRM Reporting RdlHelper Error in SSRS Report

ERROR WHILE LOADING CODE MODULE ‘MICROSOFT.CRM.REPORTING.RDLHELPER’. COULD NOT LOAD FILE OR ASSEMBLY ERROR IN REPORT INSIDE DYNAMICS 365

 

Today I found this issue when trying to compile a FetchXML-based report in Visual Studio 2015 I got an error. So this story starts when I downloaded a working rdl file from MS CRM D365 and made some minor changes in it inside the visual studio. I was trying to preview this existing report in Visual Studio 2015 I got this following error:

After banging my head for some time, I found that this issue occurred due to the Assembly version of Microsoft.Crm.Reporting.RdlHelper,

TO FIX THIS ISSUE FOLLOW THE BELOW STEPS:
  1. Click on Report rdl file in solution explorer.
  2. Go to the Report section in the header in visual studio.
  3. Click on Report Properties, It will open property section.

Now go to References Tab and browse to the correct version of the assembly in the BidExtensions folder, even if the Microsoft.Crm.Reporting.RdlHelper is listed, it may be that this is the wrong version…

The earlier version of Microsoft.Crm.Reporting.RdlHelper was 7.0.0.0 so we need to update it to 9.0.0.0 in my case.

In our case it was located here C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.Crm.Reporting.RdlHelper\v4.0_9.0.0.0__31bf3856ad364e35

although the exact location will depend on which version of the helper you have installed.

Remove any pre-existing references (which are not necessary or maybe different version of the dll).

I hope this will help you in solving your issue, signing off!

2-2

Dynamics 365 CRM 2016 Installation

Overview

This document shows the installation process of Dynamics 365 CRM 2016 installation and configuration with reporting services extension.

Prerequisite

  1. Prepare vms for SQL and Dynamic 365 Server
  2. Create and assign permission to service account (SQL & CRM)
  3. Installation Media files for installing the sql and dynamics crm

System requirement for 8.2 & 9.0

  • Software requirements
  • Hardware requirements

Note*- Refer this document for recommended software and hardware requirements

Installation Steps

  1. Create an Organizational Unit in active directory to stores all service account
  2. Create Service accounts and assign permissions
  3. Install and configure SQL server
  4. Install and configure Dynamic CRM 2016

Note* Installation steps will be the same for both types of CRM versions, With this installation, we are assuming the Active Directory domain controller setup is already.

Software requirements for 8.2

Windows Server

This version of Microsoft Dynamics 365 Server can be installed only on Windows Server 64-bit-based computers. The specific versions and editions of Windows Server that are supported for installing and running this version of Microsoft Dynamics 365 Server are listed in the following sections

Supported Windows Server editions

  • Windows Server 2012 Datacenter
  • Windows Server 2012 Standard
  • Windows Server 2012 R2 Datacenter
  • Windows Server 2012 R2 Standard
  • Windows Server 2016 Standard
  • Windows Server 2016 Datacenter

Important*

The following Windows Server versions are not supported for installing and running this version of Microsoft Dynamics 365 Server:

  • Windows Server 2016 Essentials
  • Windows Server 2012 Foundation
  • Windows Server 2012 Essentials
  • Microsoft Windows Small Business Server editions
  • The Windows Server 2008 family of operating systems

SQL Server

Supported SQL Server Editions

The following SQL Server Editions are supported with the recommendation that the latest Windows updates are applied.

  • Microsoft SQL Server 2012 Enterprise SP1 (x64)
  • Microsoft SQL Server 2012 Business Intelligence SP1 (x64)
  • Microsoft SQL Server 2012 Standard SP1 (x64)
  • Microsoft SQL Server 2012 Developer SP1 (x64)(for non-production use only)
  • Microsoft SQL Server 2014 Enterprise with Service Pack 2 (x64)
  • Microsoft SQL Server 2014 Business Intelligence with Service Pack 2 (x64)
  • Microsoft SQL Server 2014 Standard with Service Pack 2 (x64)
  • Microsoft SQL Server 2014 Developer with Service Pack 2 (x64) (for non-production use only)
  • Microsoft SQL Server 2016, Developer, with Cumulative Update 2 (CU2) (for non-production use only) Must have updates installed from Update Catalog
  • Microsoft SQL Server 2016, Standard with Cumulative Update 2 (CU2) Must have updates installed from Update Catalog
  • Microsoft SQL Server 2016, Enterprise with Cumulative Update 2 (CU2) Must have updates installed from Update Catalog

Important*

  • *For recommendations that help improve performance when you use SQL Server 2016 with Microsoft Dynamics 365, see Improve performance when you use Microsoft Dynamics 365 with SQL Server 2016.
  • 32-bit versions of Microsoft SQL Server database engine are not supported for this version of Microsoft Dynamics 365.
  • SQL Server Compact or Microsoft SQL Server Express editions are not supported for use with this version of Microsoft Dynamics 365 Server.
  • Microsoft SQL Server 2008 versions are not supported for use with this version of Microsoft Dynamics 365 Server.

Hardware requirements

Dynamics crm 2016 Server Hardware Requirements

Component *Minimum *Recommended
Processor x64 architecture or compatible dual-core 1.5 GHz processor Quad-core x64 architecture 2 GHz CPU or higher such as AMD Opteron or Intel Xeon systems
Memory 4 GB RAM 8 GB RAM or more
Hard disk 10 GB of available hard disk space 40 GB or more of available hard disk space

* Actual requirements and product functionality may vary based on your system configuration and operating system.

Note*

Running Dynamics 365 for Customer Engagement on a computer that has less than the recommended requirements may result in inadequate performance.

Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.

The minimum and recommended requirements are based on 320-user load simulation tests.

Microsoft SQL Server hardware requirements

Component *Minimum *Recommended
Processor x64 architecture or compatible dual-core 1.5 GHz processor Quad-core x64 architecture 2 GHz CPU or higher such as AMD Opteron or Intel Xeon systems
Memory 4 GB RAM 16 GB RAM or more
Hard disk SAS RAID 5 or RAID 10 hard disk array SAS RAID 5 or RAID 10 hard disk array

 

*Actual requirements and product functionality might vary based on your system configuration and operating system.

Maintaining Dynamics 365 for Customer Engagement databases on a computer that has less than the recommended requirements may result in inadequate performance.

The minimum and recommended requirements are based on 320-user load simulation tests.

Software requirements for 9.0

Windows Server

This version of Dynamics 365 Server can be installed only on Windows Server 64-bit-based computers. The specific versions and editions of Windows Server that are supported for installing and running this version of Dynamics 365 Server are listed in the following sections.

Supported Windows Server 2016 editions

The following editions of the Windows Server 2016 operating systems are supported for installing and running Dynamics 365 Server:

  • Windows Server 2016 Standard
  • Windows Server 2016 Datacenter

Important*

The following Windows Server versions are not supported for installing and running this version of Dynamics 365 Server:

  • Windows Server 2016 Essentials
  • Windows Server 2012 family of operating systems
  • Windows Server 2012 R2 family of operating systems
  • The Windows Server 2008 family of operating systems

SQL Server

SQL Server editions

Any one of the following SQL Server editions is required, running, and available for Dynamics 365 for Customer Engagement:

  • Microsoft SQL Server 2017 Enterprise1
  • Microsoft SQL Server 2017 Standard1
  • Microsoft SQL Server 2017 Developer (for non-production use only)1
  • Microsoft SQL Server 2016 Enterprise, with Service Pack 2
  • Microsoft SQL Server 2016 Standard, with Service Pack 2
  • Microsoft SQL Server 2016 Developer, with Service Pack 2 (for non-production use only)

Important*

Hardware requirements

Dynamics 365 Server Hardware Requirements

Component *Minimum *Recommended
Processor x64 architecture or compatible dual-core 1.5 GHz processor Quad-core x64 architecture 2 GHz CPU or higher such as AMD Opteron or Intel Xeon systems
Memory 4 GB RAM 8 GB RAM or more
Hard disk 10 GB of available hard disk space 40 GB or more of available hard disk space

 

* Actual requirements and product functionality may vary based on your system configuration and operating system.

Note*

Running Dynamics 365 for Customer Engagement on a computer that has less than the recommended requirements may result in inadequate performance.

Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.

The minimum and recommended requirements are based on 320-user load simulation tests.

Microsoft SQL Server hardware requirements

Component *Minimum *Recommended
Processor x64 architecture or compatible dual-core 1.5 GHz processor Quad-core x64 architecture 2 GHz CPU or higher such as AMD Opteron or Intel Xeon systems
Memory 4 GB RAM 16 GB RAM or more
Hard disk SAS RAID 5 or RAID 10 hard disk array SAS RAID 5 or RAID 10 hard disk array

 

Installation Steps

1. Create an Organizational Unit in active directory to stores all service account

Go to Active directory, right click on the domain, select Organizational Unit from the menu to create new OU for CRM2016.

Enter name for OU example – CRM2016

2.Create below Service accounts and assign permissions

Service Accounts Purpose
CrmSandbox   Microsoft Dynamics 365 Sandbox Processing

service account

CrmAsynchronous   Microsoft Dynamics 365 Asynchronous Processing

Service and

  Asynchronous Processing Service (maintenance)

services account

CrmMonitoring   Microsoft Dynamics 365 Monitoring service

account

CrmVss   Microsoft Dynamics 365 VSS Writer service

account

CrmDeployment   Microsoft Dynamics 365 Deployment Web Service

account

CrmAppPool   Microsoft Dynamics 365 Application Service

account

CrmAdmin Microsoft SQL 2016 Service account (same admin account)
CrmDbAgent Microsoft SQL 2016 Agent Service account
CrmDbReporting Microsoft SQL 2016 Reporting Service

Note*- Depending on the installation type we can choose to create and use the single or multiple service accounts for SQL and CRM, basically in the multi-server farm, the best recommendation to use the separate service account. But in the test or single server farm environment, we can create two accounts one for SQL service and another for CRM service instead of creating a separate one for each service. 

Let’s look at an example to create a service account

Go to Active directory & expand it, Right click on the OU(CRM2016), click on New and select User from the listed option

Enter the details of the service account, here we are creating a test svc account for example

Select Next and enter and confirm the password for this service account

Note*- follow the same steps for the rest of the service account

2.1 Assign permission to service account

Add the user account of the user who is installing Microsoft Dynamics CRM as a member of the local administrators group. To do this, follow these steps on the Microsoft Dynamics CRM server and on the computer that is running Microsoft SQL Server:

  1. Log on to the server as a user who has local administrator permissions.
  2. Click Start, point to Administrative Tools, and then click Computer Management.
  3. Expand System Tools.
  4. Expand Local Users and Groups.
  5. Click Groups.
  6. Right-click Administrators, and then click Properties.
  7. To add the account of the user who is installing Microsoft Dynamics CRM, click Add.

CRMADMIN :In our case, the crm Admin account is performing the installation of Dynamic CRM and SQL server, so we have added the crmadmin in the local administrator group by following above steps.

 

Delegate permission: For the ”CRM Admin” user who is installing Microsoft Dynamics CRM, add the following permissions to the organizational unit (CRM2016) in the Active Directory directory service. You must do this step for the OU to which you select to install during the installation of Microsoft Dynamics CRM i.e CRM2016.

Permissions

  • Read
  • Create All Child Objects

Permissions: To add the delegate permissions, follow these steps:

  1. Log on to the domain controller server as a user who has domain administrator permissions.
  2. Click Start, click Administrative Tools, and then click Active Directory Users and Computers.
  3. On the View menu, click Advanced Features.
  4. In the navigation pane, find the CRM2016 OU that we are using for the Microsoft Dynamics CRM installation.
  5. Right-click the OU, click Delegate permission, and then click on the Add button and search for CRMAdmin
  1. Once user is able to search, Add it and click on the Next for assign permission.
  2. Select “Create a custom task to delegate” and click Next
  3. Keep the default option and hit Next again
  1. In the below option, click to select the check box for the Create All Child Objects permission and click Next.

Note* By default, the Allow check box is selected for the Read permission.

Advanced permissions

  • Read Permissions
  • Modify Permissions
  • Read Members
  • Write Members
    To add the delegate permissions, follow these steps:
  1. Log on to the domain controller server as a user who has domain administrator permissions.
  2. Click Start, click Administrative Tools, and then click Active Directory Users and Computers.
  3. On the View menu, click Advanced Features.
  4. In the navigation pane, find the CRM2016 OU that we are using for the Microsoft Dynamics CRM installation.
  5. Right-click the OU, click Delegate permission, and then click on the Add button and search for CRMAdmin user.
  1. Once user is able to search, Add it and click on the Next for assign permission.
  1. Select “Delegate the following common task” and check “Modify the group membership of a group” and click Next.
  2. Click finish

2.3 Performance counter permissions

Follow these steps on the Microsoft Dynamics CRM server and on the computer that is running Microsoft SQL Server:

  1. Log on to the server as a user who has local administrator permissions.
  2. Click Start, point to Administrative Tools, and then click Computer Management.
  3. Expand System Tools.
  4. Expand Local Users and Groups.
  5. Click Groups.
  6. Right-click on Performance log user, and then click Properties.
  7. To add the accounts of the users who will run the Microsoft Dynamics CRM services, click Add.
    Service accounts : CrmApp pool, CrmAsynchronous, CrmSandbox, CrmVss

Note*- By completing above steps you have completed the permission part. Now lets move to the installation part.

  1. Install and configure the SQL server

For Dynamic CRM 8.2, We will use SQL server 2014 (See supported sql versions above)

  1. To install SQL, log in SQL server using CRM Admin account which is already permitted by adding in the local administrator group.
  2. Mount Sql server media and run the setup file
  3. Click to New SQL server stand-alon installation or add features to an existing installation.
  4. System check, Should be passed before continue
  5. Enter the SQL server key
  6. Accept the licence terms and click to Next
  7. Select SQL server feature Installation
  8. Check the following features under multiple selection and click next.
  • Database Engine Services
  • Full-Text and Semantic Extraction for Search
  • Reporting Services – Native
  • Client Tools Connectivity
  • Integration Services
  • Client Tools Backwards Compatibility
  • Client Tools SDK
  • Management studio tool

Note*- As we are using the SQl server 2014 for 8.2 version, here above listed features available to select, but when you will use SQl 2017 for Dynamics 9.0 you will need to install the management studio and reporting services features externally by running the setup individually.

  1. Provide the name of the SQL Instance
  2. Enter the service account for respected services(Ex: contoso\serviceaccount)
  3.  Select Authentication mode, here we are selecting Mixed mode authentication which means users can logon to the SQL server using both method Windows & SQL auth.
  4. Add user account for sql server administrators and click to Next
    We have added current user which is Crm Admin, Domain Administrator account and local administrator in case of any Disaster recovery.
  5.  Again click Next with default selection “Install and configure”
  6. Review the features and click to install and wait until the features are not installed with the success message, finally click finish.
  7.  After installation is finished. Search for the SQL management studio in windows search and hit to open it. Then click on connect and select database engine service.
  8.  You will see a window like the one below then click on Connect.
    As we have configured mixed mode authentication at the time of installation, you can connect with both methods(Windows & SQL server auth ), Sql server auth requires to enter the username (sa) and password(which is set with mixed mode). Restart the server.
  1. Install and configure CRM 2016
    The installation steps will be the same for both versions of the CRM 8.2 and 9.0. Please make sure Server’s Automatic update should be enabled before running the CRM setup.
    – To check it open cmdlet using key Wind+R –>Type ‘cmd’
    – Once cmd open type “sconfig”, it will open a new cmd window like below, here at number 5 you can see Windows update settings: You can change the current setting by selecting this option by entering 5 and enter. Type A for automatic and done.
    Note*- Once installation has been done you can revert back this setting to default by following the same process. The default setting is “Download only
    You can download the CRM server setup and can find trial key by clicking on the details tab from microsoft’s official site
    Microsoft Dynamics CRM Server 2016 8.0
    https://www.microsoft.com/en-us/download/details.aspx?id=50372
    Dynamics 365 Server, version 9.0
    https://www.microsoft.com/en-us/download/details.aspx?id=57478

Now let’s start the installation part –

  1. To Install the CRM setup , login to the CRM server using Crm Admin account.
  2. Mount the CRM media and run the setup ‘Setupserver.exe’
    Run Microsoft Dynamics CRM Server Setup by navigating to the directory. It is recommended to do it with Run as Administrator
  3. Welcome to Microsoft Dynamics CRM Server Setup page,On this page, we recommend that you click Get updates for Microsoft Dynamics CRM, to make sure that Set Up has the most recent installation files. Click Next.If there is no update needed you can proceed with the setup by clicking Next.
  4. Product Key Information : The next step is to enter the product key. You may insert a valid commercial product key or can use trial key.
  5. License Agreement page ,On the License Agreement page, review the information and, if you accept the license agreement, click I accept this license agreement, and then click I Accept.
  6. Install Required Components If Setup detects that components are missing, the Install Required Components page appears.- If you have already installed the required components, this page will not appear.
    – If you have not installed the required components listed, you can install them now. ClickInstall. When the components are installed, the status column will change from Not Installed to Installed, and you can click Next to continue.

Note: If you are prompted to restart the computer, do so, and then start Setup again.

  1. Once successfully installing all the required components, press Next to continue with the setup.
  2. Select Installation Location On the Select Installation Location page, accept the default location or enter a different file installation location, and then click Next.
  3. Specify Server roles ,Here you can specify the server roles to install in the current server To take advantage of additional performance and scaling benefits in enterprise deployments, consider distributing specific server functionality, components, and services or server roles on different servers. Microsoft Dynamics CRM 2016 supports distribution and scaling of server roles across multiple servers.There are 2 new services as part of the Back End Server roles and the Deployment Administration Server roles. These are the Email integration Service and the VSS writer service.
Email Integration Service Handles sending and receiving of email messages by connecting to an external email server
VSS Writer Service This service provides an interface to backup and restore Dynamics CRM data by using the Windows Server Volume Shadow Copy Service (VSS) infrastructure
  1. Specify Deployment Options On the Specify Deployment Options page, select the name of the computer that is running SQL Server to use the deployment box, type or select the instance of Microsoft SQL Server that will be used to store the Dynamics CRM database (MSCRM_CONFIG) For a new installation of Dynamics CRM, we select the option Create a new deployment.
  2. Select the Organizational Unit On the Select the Organizational Unit page, click Browse to display your Active Directory structure. Select the location where you want the Microsoft Dynamics CRM organizational unit to be installed into, click OK, and then click Next. Microsoft Dynamics CRM security groups are     created in this organizational unit.
  3. Specify Service Accounts On the Specify Service Accounts page, select the security accounts for the Microsoft Dynamics CRM services, and then click Next.For each service, we strongly recommend that you select a low-privilege domain account that is dedicated to running these services and is not used for any other purpose.

Additionally, the user account that is used to run a Microsoft Dynamics CRM service cannot be a Microsoft Dynamics CRM user. This domain account must be a member of the Domain Users group.

Additionally, if the Asynchronous Service and Sandbox Processing Service roles are installed, such as in a Full Server or a Back End Server installation, the domain account must a member of the Performance Log Users security group.

There are a couple of new services in CRM 2016

Monitoring Service Monitors all Microsoft Dynamics CRM 2015 server roles that are installed on the local computer. This service is used to detect expired digital certificates that may affect Microsoft Dynamics CRM 2015 services that are running in the deployment.
VSS Writer service The Microsoft Dynamics CRM VSS Writer service provides an interface to backup and restore Dynamics CRM data by using the Windows Server Volume Shadow Copy Service (VSS) infrastructure.
In our case below service account will be used with this format domain\service ACCOUNT

contoso\CrmSandbox – Sandbox Processing service
contoso\CrmAsynchronous – Asynchronous Processing Service
contoso\CrmMonitoring – Monitoring services
contoso\CrmVss – VSS Writer service
contoso\CrmDeployment – Deployment Web Service
contoso\CrmAppPool – Application Service account

  1. Select a Web Site On the Select a Web Site page, click Create a new Web site or click Select a Web Site and select a website from the list. By default, Setup will use the default website.
    When you select the Create a new Web site option, Setup creates a new website for Microsoft Dynamics CRM. You can specify the following option:Port Number: Type the TCP port number that Microsoft Dynamics CRM clients will use to connect to the Microsoft Dynamics CRM Server 2016. The default port number is 5555. Click Next

Note*- We strongly recommend that you verify the status of the existing website before you specify Setup to use an existing website.If you select a network port other than a default port, ensure that the firewall does not block the port.

  1. Specify E-mail Router Settings On the Specify E-mail Router Settings page, in the Email Router server name box, type the name of the computer where the Email Router will be installed.This computer will route Microsoft Dynamics CRM email messages. If you will not install the Email Router you can leave this box blank. However, if you install the Email Router later you must add the computer where the Email Router service is running when you use Local System, or if you use a domain user account, the account, to the PrivUserGroup security group. Click Next

Note: If you want to use Server Side Synchronization or do not want to specify the email router name you can leave it blank and click Next

  1. Specify the Organization Settings, On the Specify the Organization Name page, specify the following information.
    – In theDisplay Name box, type the name of your organization.
    – In theUnique Database Name box, you can keep the name that is automatically generated or you can type a unique name that must be limited to 30 characters. Spaces and extended characters are not allowed.Important: After Setup is complete, you cannot change the database collation, base ISO currency code, or the organization unique name. However, you can change the base currency name and base currency symbol.
  2. Specify Reporting Services Server On the Specify Reporting Services Server page, type the Report Server URL. Make sure that you use the Report Server URL, not the Report Manager URL.To verify that you are using the correct URL, in a browser, type the Report Server URL as the address.Click Next
  3. Help us Improve the Customer ExperienceOn Help Us Improve the Customer Experience page, select whether you want to participate in the Customer Experience Improvement Program, and then click Next
  4. Select Microsoft Update Option page On the Select Microsoft Update Option page, you must select either of the following options.Use Microsoft Update when I check for updates (recommended) – By selecting this option, Microsoft Dynamics CRM Server will use the Microsoft Update settings on the computer. I don’t want to use Microsoft update- You should only select this option if the computer uses another method to install updates such as by using Microsoft Windows Server Update Services (WSUS).
  5. System Checks This page is a summary of all requirements and recommendations for a successful installation. Errors must be resolved before installation can continue. If no errors, or only warnings appear, you can continue with the installation. To do this, click Next
  6. Ready to Install Microsoft Dynamics CRM, Review the Ready to Install Microsoft Dynamics CRM page, and then click Back to correct any warnings. When you are ready to continue, click Install.
  7. The installation will take sometime, one installation is finished you will see a screen like below.

Dynamics CRM Installation is completed…….
Run this link on the server and give your credentials of CRM administrator

http://myservername (in case default site chosen at the time of installation at 13th step)

https://myservername:5555 (When we select the option to create new site at 13th step.)

Install Microsoft Dynamics CRM 2016 Reporting Extensions

You must complete Microsoft Dynamics CRM Server Setup before you run CRM Reporting Extensions Setup. You must run Microsoft Dynamics CRM Reporting Extensions Setup on a computer that has a supported version of Microsoft SQL Server Reporting Services installed

You can locate the setup file from ..\Server\amd64\SrsDataConnector folder, double click SetupSrsDataConnector.exe

  1. Welcome to Microsoft Dynamics CRM Reporting Extensions Setup Select whether you want to update Microsoft Dynamics CRM Server Setup. We recommend that, if updates are available, you let Setup download the latest version.To do this, click Get updates for Microsoft Dynamics CRM, wait until the update process is complete, and then click Next
  2. License Agreement Review the information and, if you accept the license agreement, click I accept this license agreement, and then click I Accept.
  3. Install Required Components If Setup detects that components are missing, the Install Required Components page appears.
    3.1  If you have already installed the required components, this page will not appear.
    3.2 If you have not installed the required components listed, you can install them now. ClickInstall. When the components are installed, the status column will change fromMissing to Installed, and you can click Next to continue.
  4. Specify Configuration Database Server If you are using the default instance of SQL Server, enter the name of the computer that is running SQL Server and contains the Microsoft Dynamics CRM configuration database that is named MSCRM_CONFIG, and then click Next.
    Note: If you are not using the default SQL Server instance, enter <machine-name>\<instance-name>
  5. Specify SSRS Instance Name Select a Microsoft SQL Server Reporting Services instance that will be used for Microsoft Dynamics CRM reporting, and then clickNext.
  6. Select Microsoft Update Option Select whether you want to use Microsoft Update for checking for updates for your Microsoft products, and click Next.We recommend that you use the Microsoft Update to check for updates because this keeps your computer up-to-date and secure.
  7. Select Installation Location Click Browse, and select a path where you want to install CRM Reporting Extensions, and then click Next.
  8. System Checks This page is a summary of the requirements for a successful CRM Reporting Extensions installation.
    – Errors must be corrected before installation can continue. All errors must be resolved.
    – If no errors or only warnings appear, you can continue with the installation.
    To do this, click Next.- You may get the below error id the Microsoft SQL Server 2014 Reporting Service was installed via default settings- then the service account is set to Report Server
  1. To resolve the issue, open the Reporting services configuration manager and update the Service Account to something else such as “NetworkService”Once you click on Apply, you will be prompted for the File Location and the password of the Back Encryption Key. Click Apply and Exit
  1. Ready to install Microsoft Dynamics CRM Reporting Extensions Review this page, and then click Back to correct any errors. When you are ready to continue, click Install.

Microsoft Dynamics CRM Reporting Extensions Setup Completed Click Finish Thanks…….

Reference links –
Compatibility with Microsoft Dynamics CRM 2016
https://support.microsoft.com/en-in/help/3124955/compatibility-with-microsoft-dynamics-crm-2016

Microsoft Dynamics 365 Server hardware requirements
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/microsoft-dynamics-365-server-hardware-requirements

Software requirements for Microsoft Dynamics 365 Server
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/software-requirements-for-microsoft-dynamics-365-server

Dynamics 365 Installation – Hardware and Software requirements
https://community.dynamics.com/365/b/mfasih365crm/posts/dynamics-365-installation-part-2-hardware-and-software-requirements

Microsoft Dynamics 365 system requirements and required technologies
https://www.inteltech.com/wp-content/uploads/2017/01/Dynamics-365-system-requirements.pdf

Microsoft Dynamics 365 On-Premises Cumulative Updates
https://support.microsoft.com/en-us/help/3142345/microsoft-dynamics-365-onpremise-cumulative-updates

What’s New in Microsoft Teams | Microsoft Ignite 2019

New innovations in Microsoft Teams enhance collaboration and business processes for all workers

Today at Ignite, we are announcing a ton of new capabilities in Teams to help customers in all industries work in new ways and better respond to the evolving needs of their business.

Customize your Teams conversations and experience

Private channels enable users to create channels within existing teams that can be viewed and accessed by only select members of that team. Users can create a private channel by selecting “Private” under the privacy settings of the new channel. Private channels are available starting this week and you can learn more here.

The multiwindow capability provides users the option to pop out chats, meetings, calls or documents into separate windows to help you streamline their workflow. Multiwindow capabilities will start rolling out early next year.

Teams client for Linux will support the main Teams capabilities like chats, meetings, calling as expected so people who use Linux client at work or educational institution can collaborate with others on Teams. Users will be able to install native Linux packages in .deb and .rpm formats. Teams client for Linux will start rolling out as a preview later this year.

New messaging extensions including Polls and Surveys will be available in Teams chat and channel conversations. Click on “…” at the bottom of the message compose box in a chat or channel to access these extensions and solicit instant feedback on shared items or questions. These will start rolling out later this year.

Pinned Channels allows users to keep important channels at the top of your teams list for easy access. This capability will be available later this year.

Easily manage conversations, tasks, and files from other Microsoft 365 apps within Teams

New integration between Outlook and Teams makes it easy to collaborate no matter where the conversation is taking place. The user can move an email conversation from Outlook, including attachments, into a Teams chat or channel conversation by clicking on the ‘’Share to Teams’’ in Outlook. They can also share a conversation from Teams to an Outlook email by clicking on the more options (‘’…’’) icon in a conversation. This will start rolling out early next year.

Users will also get actionable missed activity emails which make it easy to stay on top of missed conversation in Teams. The missed activity emails show the latest replies from the conversation, and allow you to respond directly from within Outlook.

Tasks in Teams gives you a new unified view of your personal and assigned tasks within Teams. It consolidates your tasks across Microsoft To Do, Teams channels, Planner and Outlook. Users have smart views including tasks assigned to you, the priority as well as start or due date. Users can choose the view that works the best for them – list, boards, charts, schedules – to get things done. It will be available to users early next year.

The new Yammer app for Teams makes Yammer communities, conversations, and live events accessible right within Teams. IT admins and end users can also pin the app on the left navigation rail in Teams to have easy access to Yammer – helping everyone stay up to date with their communities and participate in organization-wide conversations. It will start rolling out early next year.

Conduct more inclusive and effective meetings

Microsoft Whiteboard is now generally available in Teams Meetings via the share tray. This gives teams an infinite digital canvas for meeting participants to ideate and collaborate whether they are in the same room or working remotely.

Live Captions in Teams Meetings makes meetings more inclusive, giving participants another way to follow along with the conversation, and addressing the needs of participants with different hearing abilities or language proficiencies. It will start rolling out as Preview in US English later this year with plans to expand to other languages in the future.

New presenter and attendee controls allow meeting organizers to pre-define presenter and attendee roles for meeting participants. Designated presenters will have full control over the meeting, whereas participants in “attendee” role won’t have ability to share content, take control, mute or remove other participants, admit people waiting in the lobby, or start/stop recordings. It will be available later this year.

Together with Citrix, we are optimizing the performance of Microsoft Teams Calling and Meetings for Citrix virtual environments allowing organizations to deliver a high-fidelity Microsoft Teams experience for an on-premises or Azure hosted virtual desktop or application. We expect this solution will become generally available to customers within the next 30 days.

Expanding the Cloud Video Interop (CVI) partnerships to include Cisco the newest partner to help customers use Teams meetings with Cisco Webex Room devices and SIP video conferencing devices in the meeting rooms, starting in early CY 2020.

With support from industry vendors, Microsoft has pioneered a new approach that enables Microsoft Teams Rooms devices to connect to meeting services from other vendors via browser-based technologies. Microsoft is working with Cisco and Zoom to enable a direct guest join capability from the respective video conferencing devices to the video meeting service using the web app. This capability will be supported on a new generation of meeting room devices with embedded web technology. We plan to add support for other vendors over the course of time. These solutions are expected to be generally available in early 2020.

Collaboration bars for Microsoft Teams are a new category of devices from our partners to convert small spaces into online meeting and collaboration spaces. These affordable, simple to install and easy to manage video conferencing solutions attach to your displays, TVs or touchscreens in minutes for high-quality video meetings. It enables experiences like one-touch & proximity join, content sharing and whiteboarding.

Poly with their Studio X Series and Yealink with VC210 are first two partners to launch their devices in early 2020.

New Microsoft Teams speakerphones have a dedicated Teams button which gives users the ability to have a seamless interaction with Teams. The first speakerphone to be certified is available from Yealink CP900 today, which will soon be followed by additional speakerphones built for Teams from our other peripheral partners. Additionally, we are offering 20% off all phones and peripherals which are certified for Teams during Microsoft Ignite. To take advantage, just add the promo code MSIGNITE19 at checkout on office.com/teamsdevices between November 4th, 2019 to November 15th, 2019

New enterprise Phone System capabilities, such as emergency calling, call queue functionality, administrative control, Phone System for Government customers like GCC High and DoD, as well as advanced functionalities like music on hold, call delegation and voice mail management will be available by end of this year. Additionally, we also announced new ISV partner enterprise voice advancements like Contact Center and Compliance Recording that make Teams Phone System a great cloud phone system solution for enterprise customers. You can find more information in the Teams Calling blog.

Learn more about Microsoft Teams devices here.

Give your Firstline Workers easier access to Teams

SMS Sign-In gives Firstline Workers a low friction way to sign into Teams with their phone number and a one-time SMS passcode for authentication. It will be available as a public preview early next year.

Off shift access is a new setting that can be enabled by IT administrators to provide a notification to Firstline Workers when they access the Teams app on their personal device outside payable hours. The users then need to provide consent to the notification before being able to access their app. It will start rolling out early next year.

Global Sign-Out saves time and keeps Firstline Workers secure when they use shared devices at work by enabling them to sign-out at once from all the apps they use on their shift. This feature will initially be available as a public preview for Android devices early next year and in preview for iOS devices thereafter.

Delegated User Management enables Firstline managers to manage user credentials and approve password reset requests via the My Staff portal. As a result, Firstline managers are empowered to unblock staff issues, reducing the burden of identity management on IT. It will be available as a public preview early next year.

Graph API enhancements provide two-way communication between a workforce management system of your choosing and Shifts to enable enterprise-scale configuration. And with new open source integration templates on GitHub, customers can integrate Teams with Kronos and JDA. JDA connectors are available now and Kronos coming later this month.

Enable industry-specific scenarios in healthcare and other industries

Virtual Consults offers a simple way to schedule and conduct B2C virtual consultations via Microsoft Teams, such as healthcare patient consults, client meetings, or job candidate interviews. Attendees can easily join the virtual consultation via their web browser or Teams mobile app. Teams has enabled virtual consults through its new external appointments functionality and is now in private preview.

Patient Coordination in Teams enables healthcare professionals to streamline patient care. By entering patient information into Teams’ secure platform, physicians, nurses, and other care team members can centralize and digitize the information they need when communicating and collaborating around patients in various scenarios like patient rounding, multi-disciplinary team meetings, and discharge huddles. Patient Coordination in Teams supports enterprise-grade security and enables HIPAA compliance. It will be available in public preview soon.

New planning and administration tools to easily manage Teams and protect your data

Advisor for Teams assists IT admins in planning a successful Teams deployment for their organization, offering recommended plans and a collaboration space for the deployment team to streamline the roll out of all the Teams workloads, including messaging, meetings and calling workloads. This feature is currently in public preview.

Microsoft Teams in Office 365 Business & Office 365 ProPlus semi-annual channel will streamline your Teams deployment with Office ProPlus. Starting on January 14th, 2020, Click-to-Run will install the Teams client for all PCs on the semi-annual channel, and the client will update itself regularly from that point onward. This will be a gradual rollout over several weeks, so not all existing installations will immediately get Teams added when Office is updated.

New app catalog helps IT admins get the information they need to confidently enable apps from the Microsoft Teams admin center. The catalog provides administrators details such as name, description, certification status, publisher, and policy details for applications available in their Teams environment. The certification status within the catalog covers a 2-tiered program – Publisher self-attestation and a rigorous Microsoft 365 Certification. These programs ensure admins have full visibility into app’s security and compliance practices. This will start rolling out by end of this year.

Policy packages make it easier to assign policies and ensure your users have access to the Teams capabilities they need. IT Admins can assign a policy package, a collection of predefined policies and policy settings, to users who have similar roles in the organization. The first set of policies packages are available now and are designed for roles in the education space. We will continue to release more policy packages soon. Learn more here.

 

Policy assignment to security groups in PowerShell is also going to be available by end of this year.

Microsoft Teams Rooms in the Teams Admin Portal will allow the IT admins to manage the device inventory for your organization and do tasks such as assign configurations, restart devices, monitor and diagnose. This will start rolling out later this year.

Managed Meeting Rooms is a new Microsoft offer for managing meeting rooms as a service.  This cloud-based IT management and security monitoring service ensures that Teams meeting rooms are secured, up to date, and proactively monitored for a great in-room experience. To date, we’ve been working with more than 100 customers to manage more than 1,500 meeting rooms. The private preview will open this experience to more of you! If you’re interested in participating in the private preview, you can register your interest here.

Safe Links in Microsoft Teams, powered by Office 365 Advanced Threat Protection, now safeguards Teams messages from harmful links in real time. When a web address (URL) is shared in a private chat or channel conversation, Teams will perform a time-of-click verification of web addresses and alert users of any risk such as malware or viruses.

Other security and compliance capabilities that will be available by end of this year include support for messaging events such as deletion and edit within audit log search; the extension of information barriers policies to apply to files stored in a team’s SharePoint site; support for retention policies as short as one day within Teams retention policies; and the expansion of e-Discovery results to now include search results for keywords and the conversations around them.

Automate workflows, integrate custom apps and data insights within Teams using Power Platform

Power Apps creators can now publish their apps as Teams apps for easy use and access when working on Teams. Admins can also publish these custom apps directly to their company’s app library in Teams, making them more discoverable to users. New updates also improve the experience of adding these apps to Teams. It will start rolling out later this year.

Pinning an app created with Power Apps to Teams left rail will provide users easy access to frequently used apps in everyday use. It will be available to users later this year.

Teams-centric actions & triggers with Power Automate allows users to create new kinds of automated workflows within Teams. The user can create a trigger for specific actions when someone new joins their team, notifications within Teams when a certain keyword is mentioned, automatically set focused time and to save notes to OneNote. These will be available to users later this year.

Power BI interactive cards in Teams chat experience will help users quickly find and take actions on their data. It will start rolling out early next year.

We are committed to delivering rich and engaging experiences that help our customers to transform their work culture and business processes with Teams.

[/vc_column_text][/vc_column][/vc_row]