Quantcast
Channel: Microsoft Dynamics 365 Blog : dynamics
Viewing all 455 articles
Browse latest View live

Just released: New content for CRM 2016 spring wave

$
0
0

The CRM 2016 spring wave includes many new and exciting features! This blog shows you where to go for new information, whether you’re an admin, customizer, developer, or end user.

The official names for the spring wave releases are:

  • Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1
  • Microsoft Dynamics Marketing 2016 Update 1
  • Microsoft Social Engagement 2016 Update 1.5

Microsoft Dynamics CRM

What’s new (all features)

Field service

Project service

CRM portals

Mobile offline

Power BI

Subscription and release history

For developers

Microsoft Dynamics Marketing

Microsoft Social Engagement

Quick references

Microsoft Dynamics CRM Content Publishing Team


How to configure SLAs

$
0
0

Hey, congrats on updating to Microsoft Dynamics CRM Online 8.1. Of the many new and exciting features, you now have the capability to use service level agreements (SLAs) for entities apart from Case. The additional entities with the SLA capabilities are:

  • All activity entities (email, appointment, etc.) except recurring appointment
  • Account
  • Contact
  • Order
  • Invoice
  • Quote
  • Opportunity
  • Lead
  • And yes, custom entities and custom activities as well :)

 

I am assuming you are already adept with configuring SLAs for Cases.

Fair assumption? Good!

Unlike cases, however, you will need to do some extra steps for configuring SLAs on the above entities. This is because you will not get the out of the box SLA KPIs for the above entities. You will have to create your own SLA KPIs, timers, and quick view forms.

Here are the steps that you need to follow for configuring SLAs on the above entities. Though you can get this information from the official documentation (Enable entities for service level agreements (SLAs), Define service level agreements (SLAs), and Add a timer to forms to track time against enhanced SLAs), there are a few places you might want to watch out for while configuring SLAs (that’s why this blog :) ). Let’s take Account as an example and learn how to configure SLAs for it.

First, you would need to enable Accounts for SLAs. (It is not enabled out of box)

  1. Navigate to Settings > Customizations > Customize the System > Entities > Account
  2. In the Communication & Collaboration section, you will see a checkbox ‘Enable for SLA’. Check, Save and Publish.
  3. Note that this is already checked for Cases out of box.

A few words of caution! SLA needs a committed relationship. Once you have selected that checkbox and saved, (by the power vested in you by Dynamics CRM and the position of a configurator) SLA cannot be disabled for the entity.

 

Enable entity for SLA

 

The second step is to create SLA KPIs for this entity.

  1. In the same Customization window, expand the SLA KPI Instance entity.
  2. Click 1: N Relationships.
  3. Click the New 1-to-Many Relationship button. The new relationship form opens.
     
     
    New 1 to Many Relationship
     
     
  4. Select Account <entity> in Related Entity dropdown.Here is a catch! As soon as you select Account in the Related Entity dropdown, the Name field gets auto populated to “new_ slakpiinstance_account”.You can use it as it is, but you will face issues if you want to export the SLAs created in this org to an org that also has SLAs enabled for Account. This is because while importing the SLAs, the system will attempt to create this relationship in the target org. Since there will be a relationship already existing in the target org, the import will fail. So it is strongly recommended to add a different name or change the name to a GUID (with underscores).
     
     
    Relationship definition_Name
     
     
  5. Fill the Display Name to your taste.
     
     
    Relationship definition_Display name
     
     
  6. Save and close.

For Cases, you’ve got 2 KPIs out of the box (First Response in and Resolve by). You will need to create similar additional KPIs if your business demands.

One of the best things about SLAs is the use of timers to indicate the time left for the SLA to be noncompliant. You can use timers for these entities too. You have it out of the box for Case but you will have to configure it for the new entities you enable for SLA.

 

Let’s see how to configure the timer.

  1. Go to SLA KPI Instance > Forms.
  2. Create a new Quick View Form.
  3. On the Insert tab, click Timer to add a timer on this form with the values of Data Source section illustrated below.
     
    Timer control 

 

A couple of things to remember.

  1. The quick view form is automatically named to “New Form”. It is strongly advised to rename it to something identifiable such as (Account SLA QV). Else, you will get confused which one to use if multiple entities are configured with SLA. [Names not so important? Go on reading]
  2. For each KPI, you will have to create a quick view form with timer. So if you have multiple entities to configure, this can get boring. Here is a quick tip for making your life easier. You will have to apply minimal effort if the SLA name and label is same across all your entities, else you will just have to edit these. Oh, I didn’t tell you the trick. The trick is to create one quick view form manually and then use Save As option to create copies. This way the Data Source section will not have to reconfigured (at least). Also the name of the form will be distinct and easily identifiable as you will be giving appropriate names while you use “Save As”.

 

SLA KPI Instance Form

 

The final configuration step

Now you need to put the controls on the entity form so that you can see the timer at the runtime. A few other relevant fields will be placed.

You could apply SLAs to Cases by either default SLA, entitlement or manually using SLA lookup. In all above entities, you cannot use the out of box entitlements. You will have to have a default SLA or use SLA lookup.

We will place the SLA lookup, SLA KPI Instance quick view form and SLA KPI Instance sub grid on the Account form.

  1. Click Accounts > Forms > Account on the same customization window.
     
     
    Navigate to Account form
     
     
  2. Drag SLA field from the Field Explorer to place the SLA lookup field.
     
     
    Account form ediitor
     
     
  3. Insert corresponding SLA KPI Instance Quick View form using the created SLA KPI Instance relationship above and correct quick view form containing the timer. If we do not rename the quick view forms while creating, we will have multiple forms in the Quick View Form lookup with the same name ‘New Form’ making it difficult to recognize the correct form. [You can thank me now :) ]
     
     
    Quick view control properties
     
     
  4. You may also want to insert a sub grid to view all active SLA KPI Instances when SLA is applied to this record.
     
     
    Set SLA KPI instance properties
     
     
  5. Save and close.
  6. Publish all customizations (Or go and publish individual customizations).

 

Phew! Configuration complete… :)
 
Now let’s create SLAs.

  1. Go to Settings > Service Management > Service Level Agreements
  2. Type a name for the SLA and select the entity for which you’re creating the SLA from entity dropdown. Note that only those entities that are enabled for SLAs will be listed here.
     
     
    Create SLA
     
     
  3. Click OK.
  4. Choose correct date time field in the Applicable from field.
  5. Click Save.
  6. Add SLA Items. Save the form.
  7. Click Activate.
  8. If you want to make this SLA default, you can click Set as Default on the command bar. You can have one default SLA per SLA-enabled entity.
  9. Next you can configure the SLA Pause states for each SLA-enabled entity.
    1. Click Service Configuration Settings (Settings > Service Management > Service Configuration Settings)
    2. Select your entity and the corresponding status reasons (belonging to active state) which will pause SLA time calculations.

 

Voila! Enjoy SLAs!

 
Account form

 

 

Cheers!

Shashank Shekhar

New Office 365 Admin center brings changes to CRM Online notifications

$
0
0

Office 365 is well underway in transitioning to a new admin center. See: Announcing the new Office 365 admin center. You’ll need to make some changes in how you view CRM Online service status and notifications.

Old Office 365 Admin center

Service health broken out by components appeared under Service Health. We have simplified service health status and this level of detail will be deprecated.
 
Service health broken out by components

Planned Maintenance notices appeared under Planned Maintenance. This has moved to the Message Center.
 
Planned maintenance notices

 

New Office 365 Admin center

Starting June 6th, 2016, Planned Maintenance notifications will now live in the Office 365 Message Center, along with the other change notifications about the customers Dynamics and Office 365 services.

Click Service health to get information on all your Office 365 services.
 
New Office 365 Admin Center

Click on a service with an alert to get detailed information.
 
See detailed information of an alert

Click View history to see a calendar with the past 30 days of service. Select a date and see service health status and details for that day.
 
View history

View Planned Maintenance notifications and other informative messages in the Message center.
 
Message Center

 

Additional Resources

How do I check my online service health?

What’s the Office 365 admin center and how does it relate to CRM Online?

Sign in to CRM Online services

Add Office 365 Online services

 

 

Microsoft Dynamics CRM Content Publishing Team

Microsoft Dynamics CRM improves iOS mobile security options

$
0
0

Given the increasingly mobile and connected nature of business in today’s world, Microsoft has enhanced the mobile security options available with Microsoft Dynamics CRM. With the latest release of CRM, we have enabled Intune Mobile Application Management for the CRM iOS mobile application.

In addition, to support this capability, Dynamics CRM is now integrated with the latest version of the Active Directory Authentication Library (ADAL) SDK for Android and the latest Microsoft Intune SDK. We have also updated our iOS support requirements to better align with ADAL and Microsoft Intune, and Dynamics CRM now supports iOS versions 8.1 and above.

For more information, see these topics:

 

 

Microsoft Dynamics CRM Content Publishing Team

Deprecation announcements with Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1

$
0
0

In order to continue to provide great capabilities for people using Microsoft CRM we occasionally need to replace older capabilities with better ones. Because these changes can be disruptive we provide as much advance notice as we can so that you can be ready to make any necessary transition. When a feature is deprecated it means that we intend to remove it at some future point, but for the time being it will continue to work and remain fully supported. You should focus on using the newer capabilities for any new work you begin and start planning for how you can move any existing deployments using the deprecated features to the better ones which will replace it.

Most recently we have documented these changes in these topics on MSDN and TechNet respectively:

These topics focus on the areas of interest to technical audiences. The MSDN topic focuses on areas of interest to developers, while the TechNet topic highlights changes that administrators and IT professionals should know about. There is some overlap, so if you participate in both of these roles, you should read both. This post will call out the major changes and include links to the sections of these topics where you can learn more.

Deprecation of the Microsoft Dynamics CRM 2011 endpoint

As described in Microsoft Dynamics CRM 2011 endpoint, the Dynamics CRM 2011 endpoint is deprecated in favor of the Web API. Deprecating an endpoint is a pretty big deal, especially when the programming model is as different as it is with these two endpoints. We strongly encourage developers to use the Web API for applications that connect to CRM. For plug-ins and workflow assemblies you can continue to use the SDK assemblies. In coming releases we will modify these assemblies so that they will use the Web API instead of the 2011 endpoint.

Updates to the CRM SDK assemblies

As described in Updates to the CRM SDK assemblies, we will be updating the SDK assemblies we have shipped for CRM versions going back to CRM 2011. There are some changes to the underlying security architecture for CRM Online which we have already applied to the assemblies shipped for the most recent release. Any applications using older assembly versions to connect to CRM Online will need to be re-linked to the updated assemblies to function normally.

Removal of the Use legacy form rendering option

As described in Removal of legacy form rendering option, we will remove ability to use legacy form rendering. This means that that the improved form rendering introduced with CRM Online 2015 Update 1 will be used for all forms.  This different rendering changes the underlying document object model (DOM) of the pages and can break scripts using unsupported methods. We are also aware that there have been some behaviors in the supported Xrm.Page client object model that are not fully backward compatible. If you have used this option, you should start testing your forms with this option turned off and disable any unsupported scripts to understand whether the undesirable behavior is due to unsupported scripts or a backward compatibility problem. If this is a backward compatibility problem, please contact CRM technical support to get help about resolving the issue.

Deprecation of some knowledge management entities

As described in Some knowledge management entities, we are deprecating three knowledge management entities in favor of the new KnowlegeArticle entity introduced in CRM Online 2016 Update and CRM 2016.

Removal of support for older Android versions

As described in Removal of support for some Android versions, we are removing support for some older versions of the Android operating system with future versions of Microsoft Dynamics CRM for Android.

Reminder that the Microsoft Dynamics CRM List component is deprecated

Finally, as described in Microsoft Dynamics CRM List Component is deprecated, we want to remind you that customers currently using the Microsoft Dynamics CRM List Component for SharePoint Server are advised to upgrade to use server-based Microsoft SharePoint integration.

Please be aware of these changes so that you can take advantage of all the improved capabilities we are continually adding the Microsoft Dynamics CRM.

 

Microsoft Dynamics CRM Content Publishing Team

Automatic Case Creation from Community Forums using SLA

$
0
0

With the web portal capabilities in CRM 2016 Spring Wave, you can extend CRM to the web to deliver exceptional customer service and increase customer engagement and satisfaction. With the community portal, you can enable peer-to-peer interactions between experts in the community, subject matter experts within an organization, and internal and external users. Communities organically grow the catalog of available knowledge from knowledge base articles, forums, and blogs.

Integration with Dynamics CRM provides the flexibility to automate business processes based on information originating from web portal that gets tracked in CRM. For example, you can use the SLA functionality to enable automated case creation in CRM if a forum thread has not been answered for 10 days (or if the forum thread size increases beyond a certain limit while it is still unanswered). This can help ensure that you are addressing all customer queries wherein a peer-to-peer interaction is unable to resolve it in a timely way.

Following are the steps using which you can enable this scenario:

 

Step 1: Enable Forum Thread entity for SLA

Navigate to Settings -> Customizations -> Customize the System, and then enable the flag “Enable for SLA” on the Forum Thread entity as shown in the below screenshot.

 

1_Enable Forum Thread For SLA

 

Step 2: Create SLA KPI

Before creating SLA for a custom entity, you must ensure that you have created SLA KPI(s) for the custom entity. This can be done by creating a look up field with target record type set to SLA KPI Instance entity.

Create a new lookup field “Forum Thread Answered (SLA KPI)” (with target record type set to SLA KPI Instance) on the Forum Thread entity after navigating to Settings -> Customizations -> Customize the System. This SLA KPI will be used to ensure that a forum thread gets answered on time. You may take a look at the below screenshot for reference.

 

2_Create SLA KPI

 

Step 3: Mark Forum Thread and Form Thread Type entity fields as Searchable

Mark the field “Answered?” of entity “Forum Thread” as searchable as shown in the below screenshot.

 

3_Mark Answered as Searchable

 

Mark the field “Requires Answer” of entity “Forum Thread Type” as searchable as shown in the below screenshot.

 

4_Mark Requires Answer as Searchable

 

Step 4: Create a field to check case creation on Forum Thread

Create a new lookup field “Case Created?” with type set to “Two Options” as shown in the below screenshot. This field can be used to check if a case was already created for a forum thread (to avoid creating duplicate records).

 

5_Create field to check case creation

 

Step 5: Create a field to track associated forum thread on case

Create a new lookup field “Forum Thread” with Target Record Type set to “Forum Thread” as shown in the below screenshot. This is used to set the forum thread reference on the case that got created. You must publish customizations after you create this field.

 

6_create field to track associated forum thread

 

Note: You can optionally use create a quick view form on forum thread entity, and show more information from the forum thread on the case form using this quick view form.

 

Step 6: Create an SLA

Navigate to Settings -> Service Management -> Service Level Agreements, and click on New to create a new SLA on Forum Thread entity.

 

7_Create SLA

 

Specify the general SLA information as in the screenshot below, and Save the record.

 

8_Specify general SLA information

 

Create a new SLA Item in the SLA Details section to create a case if the post count in a forum thread (that requires an answer) exceeds or is equal to 5 posts, and a case hasn’t been created already.

 

9_Create a new SLA item

 

You can use the following Applicable When condition for this:

 

10_Add Applicable When conditions

 

Set the success criteria to check if the forum thread has been marked as answered.

 

11_Add success criteria

 

Ensure that the failure after and warn after are set to 0 minutes. This will ensure that the case gets created as soon as the post count reaches 5.

Add a failure action to create a new case. Update the case title, customer, description, forum thread reference using dynamics values as shown below.

 

12_Case details for the new case in failure action_1

12_Case details for the new case in failure action_2

12_Case details for the new case in failure action_3

12_Case details for the new case in failure action_4

 

Add another failure action to update the forum thread record to set the field “Case Created?” to Yes. This will ensure that no multiple cases get created for the same forum thread using this SLA (when it gets re-evaluated).

 

13_Add failure action to set Case created to Yes

 

You can add more failure actions e.g. Send an Email to the Community Manager regarding the case that gets created, etc.

From the SLA record form, add another SLA Item to create a case if a forum thread (that requires an answer) remains unanswered for 10 days.

 

14_Create a new SLA item for forun threads unanswered for 10 days

 

You can use the following Applicable When condition for this:

 

15_Add Applicable When conditions for the second SLA item

 

Set the success criteria to check if the forum thread has been marked as answered.

 

16_Add success criteria for the second SLA item

 

Ensure that the failure after is set to 10 days. This will ensure that the case gets created only if the forum thread has not been marked as answered for 10 days after it got created. You can set warn after to 0 minutes.

Add failure actions as specified for the earlier created SLA Item.

Save the SLA record, and activate it. Make sure that you click on Set as Default to ensure that the SLA gets applied to all forum threads that get created in the organization.

This completes the setup of this scenario wherein case creation can be automated using SLA if forum threads do not get answered on time, or if the forum thread size increases beyond a certain limit.

 

 

Cheers!

Hemant Raj

 

 

Launching the New ideas portal for CRM

$
0
0

We are excited to announce that today we launched the new ideas portal for CRM and its family of products.

Launching the new ideas portal for CRM

Help us to improve Microsoft Dynamics CRM and its family of products and solutions by discussing ideas, providing suggestions, and giving feedback. This tool uses the ideas module of our community portal solution with Microsoft Dynamics CRM backend. You will have access to the following forums on this site.

Microsoft Dynamics CRM

Microsoft Dynamics Marketing

Microsoft Social Engagement

Parature, a Microsoft Company

Use these forums to submit your product ideas and suggestions. Search the forums to see if your idea already exists. If it does, you can vote for it and add comments. If your idea isn’t there, submit it. Your feedback goes to the teams working on these products and features. Read the posting guidelines and FAQs for more details.

With the launch of this portal, we are discontinuing the legacy “Dynamics Product Suggestion” connect site as our ongoing product suggestions site for Microsoft Dynamics CRM, Microsoft Social Engagement and Microsoft Dynamics Marketing. The Preview team will continue to use the “Preview” Connect site to take Preview related feedback and support tickets.

Removal of List Component

$
0
0

In May 2015, we announced the List Component deprecation as a result of SharePoint’s deprecation of the sandbox solution, a dependency of the List Component.  Recently, SharePoint has announced the removal of code-based sandbox solutions in SharePoint Online.

Customers using the List Component with SharePoint Online are advised to migrate to the server-based integration immediately to avoid disruption of service.  Sandbox execution for the List Component is scheduled to turn off on November 30, 2016.

Here are details from SharePoint’s blog post [See Full Post]:

  • As part of the removal process, activation of new code-based sandbox solutions, as well as updates of existing solutions are no longer available.
  • In the coming weeks, running code-based sandbox solutions in SharePoint Online multi-tenant environments also will be disabled. Customers with these solutions should watch the Message Center and Service Health Dashboard (SHD) for details, timelines, and exception processes.

See Set up SharePoint integration with Microsoft Dynamics CRM for more information on enabling server-based SharePoint integration.

Customers using the List Component with SharePoint on-premises deployments are not currently affected.

 

Regards,

Jason ***


Backup and restore your CRM Online instance

$
0
0

Protecting your CRM data and providing continuous availability of service is important for you and for us. You have multiple options for backing up and restoring your CRM Online instances. For CRM Online 2016 Update 1, we’re introducing on demand backups that you can perform on CRM Online 2016 Update 1 Production and Sandbox instances.

CRM Online Administrator Center

There are two types of backups: system backups and on demand backups.

System backups

System backups take place without you having to do anything.

About CRM Online system backups:

  • All your instances are backed up.
  • System backups occur daily.
  • System backups are retained up to three days. Check your expiration date.
  • System backups do not count against your storage limits.
  • System backups are identified as created by System on the Manage backups page.

 

On demand backups

With on demand backups, you can make your own backup before making some significant customization change or applying a version update.

About CRM managed on demand backups:

  • You can back up Production and Sandbox instances.
  • You can only restore to a Sandbox instance. To restore to a Production instance, first switch it to a Sandbox instance. See Switch an instance.
  • Only CRM Online 2016 Update 1 or later versions are supported for backup.
  • On demand backups are retained for up to three days. Check your expiration date.
  • On demand backups are identified as created by someone other than System and by the presence of Edit | Delete | Restore in the details section. System backups only have Restore.

Backup and restore CRM online instance

 

 

Additional Resources

Backup and restore instances

Manage your Microsoft Dynamics CRM Online subscription

 

 

Restrict access to CRM Online with trusted IP Rules

$
0
0

Applies To: Dynamics CRM Online

You can limit access to CRM Online to users with   trusted IP addresses to reduce unauthorized access. When trusted IP address restrictions are set in a user’s profile and the user tries to log in from an untrusted IP address, access to CRM Online is blocked.

Requirements

  • A subscription to Azure Active Directory Premium.
  • A federated or managed Azure Active Directory tenant.
  • Federated tenants require that multi-factor authentication (MFA) be enabled.

Additional security considerations

IP restriction is only enforced during user authentication. This is done by the Azure Active Directory Conditional Access capability. CRM Online sets a session timeout limit to balance protecting user data and the number of times users are prompted for their sign-in credentials. Trusted IP restriction for devices (including laptops) is not applied until the CRM Online session timeout expires.

For example, a trusted IP restriction is setup to only allow access to CRM when users are working from a corporate office. When a CRM user signs in into CRM using their laptop from their office and establishes a CRM session, the user can continue to access CRM after leaving the office until the CRM session timeout expires. This behavior also applies to mobile and offsite connections such as: CRM for phones and tablets, and Dynamics CRM App for Outlook.

Create security group (optional)

You can restrict access to all Users or groups of users. It’s more efficient to restrict by a group if only a subset of your Azure Active Directory (AAD) users are accessing CRM Online.

1. Sign in to your Azure portal .

2. Click Browse> Active Directory, and then select your CRM Online directory.

3. Click Groups> Add Group, and then fill in the settings to create a new group.

Create security group

4. Click the group you created and add members.

Add members to group

 

Create a location based access rule

Access restriction is set using Azure Active Directory (AD) Conditional Access. See Getting started with conditional access to Azure AD. You control Conditional Access through an access rule.

 

Note
Setting Conditional Access is only available with an Azure Active Directory Premium license. Upgrade your Azure AD to a Premium license in the Office 365 admin center (https://portal.office.com> Billing>Purchase services).

1. Sign in to your Azure portal.

2. Click Browse> Active Directory, and then select your CRM Online directory.

3. Click Applications, and then click the Dynamics CRM Online web application.

Create a location based access rule

4. Click Configure.

Configure Dynamics CRM online

5. Set the following on the Properties page:

  • Set Enable Access Rule to On.
  • Optional: Set Apply to to Groups.
  • Optional: Click Add Group to select a group.
  • Set Rules to Block access when not at work.

Set properties for access rules

  • Click Save> OK.
  • Click Click here to define/edit your work network location.

Edit your work network location

6. Enter trusted IP addresses (using CIDR notation) and click Save.

Multi-factor authentication

See Also

How to set Azure Active Directory device-based conditional access policy for access control to Azure Active Directory connected applications

Restrict access to CRM Online with trusted IP Rules

CRM Web API sample code published

$
0
0

I’m happy to announce that we’ve just published the first set of samples for the Microsoft Dynamics CRM Web API.

The CRM Web API was released nine months ago and all of our samples so far have simply demonstrated raw HTTP requests and responses. These are the first set of samples you can download and run using the Web API. You can find information about these samples at Web API Samples.

The samples are posted on the MSDN Code Gallery. These samples are for C# and client-side JavaScript. Here is a list of this set of samples: C# and Client-side JavaScript Web API samples.

Scope of these samples

Being a RESTful OData v4 service, the CRM Web API allows developers many options about how to interact with the service—there is no single ‘correct way’ to do it. These samples are not intended to demonstrate any type of single preferred way to use the Web API. Instead, they simply provide examples that show straightforward use of the CRM Web API.

Many people have been asking for re-usable helper libraries so that they can simply put the Web API to use without having to be concerned about their inner workings. This is not the purpose of these samples.

Except for a set of C# helper libraries to manage authentication, these samples do not represent helper libraries to perform CRM data operations. These samples have been written to expose the specific low-level configurations that make the specific OData v4 capabilities we have implemented work. We have tried to keep them as light as possible, which means that we have not tried to encapsulate operations behind methods and provide a de facto helper library. Our goal is to demonstrate how these operations are performed so that developers can create their own helper libraries which align with how they wish to use the Web API.

There are a number of helper libraries for OData which you can find at http://www.odata.org/libraries/.

If you are looking for CRM specific helper libraries or code generators, please refer to these community resources:

The approach we chose

Because there are so many different approaches developers might take, we have tried to be very clear about the approach we have chosen for these samples. Each sample includes a specific set of operations which are described in a language neutral way that includes the HTTP requests and responses as well as the output of the sample.

For example, the Web API Basic Operations Sample provides the common set of operations which is implemented by both the Web API Basic Operations Sample (C#) and the Web API Basic Operations Sample (Client-side JavaScript). In the future we can provide additional samples with different languages and show how that language or technology can be used to achieve the same result.

For each language sample, we have provided details about the particular approach we chose.

  • Web API Samples (C#) describes that we chose to use the Json.NET library together with the standard .NET framework HTTP messaging classes. The C# samples do include helper libraries that manage the configuration data about the service, information about applications registration, and authentication using ADAL or Windows Authentication.
  • Web API Samples (Client-side JavaScript) topic describes how we chose to provide a basic request helper function and use a specific ES6 Promise polyfill so that the samples demonstrate the use of Promises.

What’s next?

This is just our first set of Web API samples. We intend to expand the samples available to include use of the ODataLib Client for .Net and samples using Java. We also intend to expand the breadth of operations we cover to include batch operations.

Please let us know what you think.

Jim Daly

Interested in learning how server-side sync works?

$
0
0

We have recently published the Server-side Synchronization in Dynamics CRM and Dynamics CRM Online white paper. This paper describes in detail the process for synchronizing accounts, contacts, tasks, and email between Dynamics CRM and Exchange, which is handled by the Asynchronous Processing Service.

Server-side synchronization in Dynamics CRM and Dynamics CRM Online

Download it to learn how server-side sync works!

Ben Elad

Tracking and Synchronization of Communication Activities and Contacts using Outlook and Exchange Integrations in CRM

$
0
0

Dynamics CRM has the most comprehensive Outlook & Exchange integrations in the industry. We are leaders in the industry since the beginning with a COM add-in for Outlook – CRM for Outlook.

The tracking of customer and prospect communication is a key capability for any CRM system. In sales, the salespeople have to keep track of communication with their prospects and customers for new deals or opportunities. In customer service, email is one of the important channels of communication between customer service agents and customers for the issues on products and services.

Dynamics CRM allows tracking and synchronization of the data – emails, appointments, tasks, and contacts – associated with this communication. There are two ways to track this data in CRM.

Manual Tracking

This can be done using two clients. One is through our deep integration with Outlook using a COM add-in CRM for Outlook mentioned earlier. Second is through our new lightweight client – CRM app for Outlook.

CRM for Outlook supports actions to track the items like emails, appointments, tasks and contacts. For further details, please see Overview of tracking records in CRM for Outlook. All standard operations in Outlook and Exchange such as Create, Update, Delete are supported. The user can also perform other operations in Outlook – for example, assign task to another user, and have those updates flow through tracked items.

Our CRM app for outlook only supports tracking of emails currently. However, tracking of appointments, and contacts is on our future release roadmap. The app is supported across various browsers for OWA (Outlook Web App) including Mac & Windows platforms, and devices. It also works on Outlook desktop client. In future, we will also support it on outlook mobile app. It is a zero footprint client on the client devices using Office app extensibility platform. It also supports capabilities for getting contextual information regarding the email. For further details on CRM app for outlook, please see CRM App for Outlook User’s Guide.

Not only can you track these items, but you can link them, or set them “regarding” a specific lead, opportunity, case or even a custom entity.

Automated Tracking

There are two ways to do automated tracking for received emails. One is rule based tracking. There are three rules by which you can track received emails in your inbox – all emails, or emails from your contacts and leads, or emails that are in response to tracked emails. In CRM 2015, we introduced another method called folder based tracking. The folder based tracking allows the user to create folders in Outlook or Outlook Web app or Exchange. These folders may correspond to any CRM entity record such as Opportunity, Case, Account, etc. The user can either write automated rules in exchange or outlook to move inbox emails to these folders. Our synchronization capability picks up emails in those folders for synchronization. The biggest advantage is that it can also be used with native mobile device email apps by dragging and dropping the email into these folders. Please review Track Outlook email by moving it to a tracked Exchange folder for further details.

CRM also supports converting social feeds such as a tweet (from Twitter) to a case or opportunity either manually or automatically based on sentiment or intent using integration with Microsoft Social Engagement. For further details, please review Create a CRM record from a social post.

Data Synchronization

CRM supports two ways to do bi-directional synchronization of communication activities and contacts. The items tracked using manual or automated tracking described above are picked up by our synchronization methods to synchronize with CRM. One way is through our CRM for Outlook. It uses client side outlook synchronization to do bidirectional synchronization of data. Since CRM 2013, we introduced a new method called Server-Side Synchronization which replaces email router. The server side synchronization has many benefits including reduced administration costs for our online customers.

CRM for Outlook supports both synchronization methods, but, server side synchronization is preferred. CRM app for Outlook only supports server side synchronization. In bidirectional synchronization, the data is synchronized in both directions. The changes to CRM data based on user or organizational (system) filters are synchronized with Exchange or Outlook. The changes to outlook or Exchange data based on manual or automated tracking are also synchronized with CRM. The emails, appointments and tasks are synchronized with respective activities in CRM and Outlook/Exchange contacts are synchronized with CRM contacts. The delete operation in CRM or delete/track operations in Outlook & Exchange have specific behavior. For further details on data synchronization, please review Synchronize data with Outlook or Exchange FAQ.

The synchronization can be configured at the organizational level to provide flexibility for the administrator to synchronize fields of an item in one direction, or both directions or none (Do not Synchronize). All field level security is applied for both synchronization methods. Please review help article Control field synchronization between CRM and Outlook or Exchange for further details.

CRM also provides choice to our customers by supporting all four cases including hybrid scenarios – CRM online with Exchange Online & Exchange Onpremises, and CRM Onpremises with Exchange Online and Exchange Onpremises. For further details, please review help article Supported email service configurations for server-side synchronization.

In summary, our differentiators in outlook and exchange integrations are unmatched in the industry. In our fall release we will introduce a new way to track emails in our browser clients (web client) by incorporating untracked emails from contacts and leads into our activity feed. Our roadmap also includes innovation in this space using text analytics on email body to understand user’s intent by data mining of exchange emails to get relationship insights. We shall continue to innovate on manual or automated rules for tracking and synchronization using CRM app for Outlook and Server Side Synchronization.

Microsoft Dynamics CRM 2016 Update 1 Performance

$
0
0

The Microsoft Dynamics CRM team has been testing the performance of Microsoft Dynamics CRM 2016 Update 1 (version 8.1) (on-premises) hosted on Microsoft Azure Virtual Machines. The goal is to establish a baseline for performance on Microsoft Dynamics CRM 2016 Update 1, using Azure IaaS infrastructure with premium storage.  The scenarios we have targeted involve thousands of users accessing their environment concurrently, every few minutes, with various workloads designed to simulate production.  In this new baseline, we are testing performance against a SQL DB running on VM (Azure GS5 SKU). The detailed configuration, topology, optimizations, data profile, and test workload as well as lessons we learnt along the way on how to really get your Microsoft Dynamics CRM deployment tuned will be included in a whitepaper to be published very soon.

Infrastructure and Environment Configuration 

Infrastructure and environment configuration

Microsoft SQL Server

SQL Server was deployed on an Azure GS5 virtual machine configured with 32 cores and 448 GB of memory.

Microsoft SQL Server
ProviderAzure
Virtual Machine TypeGS5 Standard
Operating SystemMicrosoft Windows Server 2012 R2 Datacenter
Processor2.00 GHz Intel Xeon® E5-2698B v3, 32 Cores
RAM448 GB

 

Microsoft Dynamics CRM Server

Dynamics CRM Server was deployed on Azure DS14 virtual machines configured with 16 cores and 112 GB of memory.

 

Microsoft Dynamics CRM Servers
ProviderAzure
Virtual Machine TypeDS14 Standard
Operating SystemMicrosoft Windows Server 2012 R2 Datacenter
Processor2.20 GHz Intel Xeon® E5-2660 v3, 16 Cores
RAM112 GB

 

Summary

From the initial round of tests, with around 15,000 concurrent users, we observed an average PLT (Page Load Time) of under a second and average transaction time for complex CRM operations staying at under a couple of seconds.  We’ve designed each of these transactions to mimic real world usage, which include scenarios like:

  • Basic user interactions like loading entity forms and manipulating grids.
  • Searching and advanced find
  • Dashboards and reporting
  • Appointment, email, phone calls, etc. (activity tracking)
  • Coverage over multiple clients (web, mobile, etc.)
  • … and more

We targeted and observed an average CPU utilization between 80-90% with these workloads for the duration of the test run.   Our aim with the white paper will be to stress test Microsoft Dynamics CRM 2016 Update 1 even more, increasing the numbers of users and test mix values to define a benchmark for on-premises installations moving forward. Also the white paper would cover the results from performance testing of Microsoft Dynamics CRM Online (v8.1), under similar load conditions.

The results reflect the scalability and performance achieved on a specific Microsoft Dynamics CRM 2016 implementation running in a particular test environment.  Actual performance may vary based on factors ranging from specific customizations deployed to geographic distribution of users and network latency/bandwidth.  Customers should expect that results will vary for each implementation and should perform their own performance testing based on their needs or requirements.  In some cases, customers may achieve higher levels of performance by fine-tuning or optimizing the configuration of Microsoft Dynamics CRM.

Additional Information

In addition to this performance test run, we have correlated the results found with those observed while performance testing Microsoft IT’s Dynamics CRM Online instances and found an improvement of about 1 second (across different internal scenarios) over the previous baseline for Microsoft CRM Online 2016 (v8.0).

With this white paper release, we aim to demonstrate the robustness of Microsoft Dynamics CRM 2016 Update 1 and its capability to handle concurrent user activities with ease for enterprise CRM scenarios.  This is the result of significant work put into this CRM release and our unwavering commitment to customers to excel on performance standards.

 

– Srikumar Nair

 

 

Sending encrypted workflow notification emails

$
0
0

Does business require to send encrypted workflow notification emails in synch with your company’s security requirements? The following steps describe how to do it using CRM Online and Office 365.

Office 365 Message Encryption requires the Azure Rights Management service. Once you have a subscription to this service, you can activate it as described in the following procedure. For more information about this requirement, see Prerequisites for using Office 365 Message Encryption.

Necessary steps:

  1. Server side synchronization configuration for your CRM Online instance
  2. Activate Azure Rights Management
  3. Set up Azure Rights Management for Office 365 Message Encryption
  4. Define rules to encrypt email messages
  5. Create a test CRM workflow and test it

1. Server side synchronization configuration for your CRM Online instance

It is assumed that server side synchronization is set up properly for your CRM Online instance using Exchange Online for outgoing emails. More information: Set up server-side synchronization of email, appointments, contacts, and tasks

2. Activate Azure Rights Management

Check whether you have an Azure Right Management subscription.:

Go to https://portal.office.com/AdminPortal/Home?switchtomoderndefault=true#/subscriptions within Office 365. You should see Azure Rights Management Premium among your subscriptions.

Activate Azure Rights Management subscription

 

If your subscription does not include it, press the +Add Subscription button and select Azure Rights Management Premium (you can buy it or start a 30-day trial):

Add Azure Rights Management Premium subscription

 

After a few minutes you should see this under Subscriptions in the Office 365 Admin Center:

Activate Azure Rights Management subscription

 

More information: how to activate Azure Rights Management (https://docs.microsoft.com/en-us/rights-management/deploy-use/activate-service)

3. Set up Azure Rights Management for Office 365 Message Encryption

Once you have Azure Rights Management, the next step is to set up Azure Rights Management for Office 365 (Exchange Online) message encryption. We will use Windows Power Shell to connect to Exchange Online and accomplish this step. (More information how to Connect to Exchange Online using PowerShell)

Open a PowerShell windows as Administrator and execute the following PowerShell commands:

Set-ExecutionPolicy RemoteSigned

$UserCredential = Get-Credential

Enter your Office 365 Global Administrator user credentials.

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUrihttps://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Import-PSSession $Session

 

Configure the Rights Management Services (RMS) online key-sharing location in Exchange Online. Use the RMS key sharing URL corresponding to your location, as shown in this table:

LocationRMS key sharing location
European Unionhttps://sp-rms.eu.aadrm.com/TenantManagement/ServicePartner.svc
North Americahttps://sp-rms.na.aadrm.com/TenantManagement/ServicePartner.svc
South Americahttps://sp-rms.sa.aadrm.com/TenantManagement/ServicePartner.svc
Asiahttps://sp-rms.ap.aadrm.com/TenantManagement/ServicePartner.svc

 

Since my tenant is located in the European Union, I use the following PowerShell command:

Set-IRMConfiguration -RMSOnlineKeySharingLocation “https://sp-rms.eu.aadrm.com/TenantManagement/ServicePartner.svc

Run the following command to import the Trusted Publishing Domain (TPD) from RMS Online:

Import-RMSTrustedPublishingDomain -RMSOnline -name “RMS Online”

To verify that you successfully configured IRM in Exchange Online to use the Azure Rights Management service, run the following command:

Test-IRMConfiguration -RMSOnline

Among other things, the command checks connectivity with the RMS Online service, downloads the TPD, and checks its validity. If everything is OK, you should see as result of the test: ‘Overall result: pass’.

Run the following commands to disable IRM templates from being available in OWA and Outlook and then enable IRM for your cloud-based email organization to use IRM for Office 365 Message Encryption.

To disable IRM templates in OWA and Outlook:

Set-IRMConfiguration -ClientAccessServerEnabled $false

To enable IRM for Office 365 Message Encryption:

Set-IRMConfiguration -InternalLicensingEnabled $true

To test the IRM functionality, run the following command, where you use your username instead of administrator@encryptedwfmail.onmicrosoft.com:

Test-IRMConfiguration -Sender administrator@encryptedwfmail.onmicrosoft.com

If everything is OK, you should see as result of the test: ‘Overall result: pass’.

More information how to Set up Microsoft Azure Rights Management for Office 365 Message Encryption.

4. Define rules to encrypt email messages

The next step is to define the conditions when we want to encrypt an email. In our case, email encryption is only needed when the body of the email contains the following phrase: ‘(This email was encrypted using Microsoft Office 365)’

It can be defined in the Exchange Admin Center (EAC), which can be accessed within Office 365 via Admin > Exchange:

From the EAC, go to mail flow> rules:

Select +> Create a new rule…

Create a new rule to encrypt email messages

 

Enter the Name (for example ‘Encrypted CRMONL workflow email’) and click on the More options… button in the opening pop-up window as shown below:

 Specify rule details

 

Then specify when the rule should be applied. So select The subject or body > subject or body matches these text patterns:

Select when the rule should apply

 

Enter the phrase (for example: ‘(This email was encrypted using Microsoft Office 365)), press the + sign and finally press Ok as shown below:

Specify words or phrases

 

The last step to set Office 365 Message Encryption by selecting Modify the message security… > Apply Office 365 Message Encryption as shown below and then press Save:

Set Office 365 Message Encryption 

 

More information how to Define rules to encrypt or decrypt email messages.

5. Create a test CRM workflow and test it

The final step is to create a workflow where we want to use the email encryption and test it in practice.

We are creating a simple workflow which is fired when an account is created and sends an encrypted notification email. Assuming that the reader is familiar with the Dynamics CRM workflow basic, the relevant parts are highlighted here.

When you define the workflow, specify the

  • Process Name: Account create – encrypted mail
  • Entity: Account
  • Category: Workflow
  • Start condition: Record is created
  • Step: Send email: Create new message

as shown below:

Define a workflow

 

And add the email properties as the following:

Specify email properties

 

The key elements of the workflow notification email is the last sentence in the message body – (This email was encrypted using Microsoft Office 365) – which should be the same string as we defined the message encryption rule.

Let’s Save and Activate the workflow, before we can test our work.

Finally, to test our work, first let’s create a new account in CRM:

Create a new account record.

 

Then we receive the encrypted account creation notification email, which is actually an html email attachment:

Encrypted account creation notification email

 

When we try to open the html file in a browser, we have two options:

  • Sign in with our Office 365 credentials or
  • Use a one-time passcode

Message when opening the encrypted message in a browser

 

Now, using the one-time passcode option, we will get another email including the one-time passcode:

Use the one-time passcode option

 

After specifying the passcode, we can read the workflow notification email:

Read workflow notification email

 

 

– Miklos Hoffmann

 

 


New Mobile Samples using Web API

$
0
0

I’m pleased to announce we have published two new mobile samples to GitHub.

Both of these samples demonstrate the same ActivityTracker functionality provided by earlier samples. They have been updated to use the Dynamics CRM Web API and they support iOS9 and Android 6 platforms. The iOS application is written using Swift 2, rather than Objective C.

ActivityTracker is a reference scenario for the sample apps. ActivityTracker helps a user quickly search for contacts, access recent contacts and easily report ‘check-in’ activities in CRM. It is designed for sales and customer service professionals to quickly access and update information on the go. With the published source code, the app can be easily modified by developers for your own scenarios and requirements.

For both samples, you will find complete instructions about how to build the sample applications. Find them here:

Learn more at https://msdn.microsoft.com/dynamics/crm/mobilesdk.

Jim Daly

Microsoft Dynamics Marketing and Our Vision for Marketing in Dynamics 365

$
0
0

In preparation for Dynamics 365 and the opportunities it opens up to our customers around the world, we have taken years’ worth of customer feedback, internal experience, and industry refinements in the marketing space to bring forth the next generation of marketing from Microsoft.  Today, we are pleased to announce that our vision for the future of marketing will be realized in our Spring 2017 release cycle with the availability of a new marketing application “Dynamics 365 for Marketing, Business Edition”.

 

The new marketing application that will accompany this release will bring our marketing automation tools and features to a whole new level, while also ensuring that they harness the power of Azure and are hyper-scalable for customers of all sizes.  While we are very excited about this release and its many features, it also means that our existing marketing application, Microsoft Dynamics Marketing, will no longer be sold to new customers as of November 1st, 2016 in order to prepare for the debut of this new application.

 

Although Microsoft Dynamics Marketing will no longer be available for purchase, Microsoft is continuing to invest in Marketing solutions.

Microsoft is planning to release a new marketing app as part of the Dynamics 365, Business edition. This solution is planned for the Spring of 2017. Pricing and licensing details will be made available prior to release. The new Marketing application will include features and benefits that Dynamics Marketing customers will find very appealing including functionality to model and manage customer journeys across marketing and sales, lead management across marketing and sales, and sharing the same Dynamics 365 platform as the Sales app.  Additionally, the Marketing app in the Spring 2017 release of Dynamics 365 for Marketing will include email marketing, event management, landing pages, and lead management.

Microsoft Dynamics Marketing customers who wish to transition to the new Dynamics 365 Marketing app should evaluate the solution in Spring 2017 and plan their transition in the following 6 to 12 months.

 

For our existing Dynamics Marketing customers, we want to be crystal clear about our intentions, what the transition between these two applications will look like, and what this means for your business.  Below is a brief summarization of the methods in which Microsoft Dynamics Marketing can be purchased today:

 

  1. MOSP (web-direct): Dynamics Marketing licenses purchased directly via the Office 365 portal
  2. CRM Online Enterprise: All existing CRM Online Enterprise licenses include Dynamics Marketing
  3. Enterprise Agreements: Dynamics Marketing licenses may have been included within your EA

 

In line with our support policy, existing customers in an Enterprise Agreement or those who have purchased licenses directly through MOSP (web-direct) will have the option to request renewal of their existing agreements until October 31st, 2017.  Existing customers can also continue to purchase additional seats and Dynamics Marketing add-on capabilities – such as additional email messages and data storage – for the duration of their agreement.  Microsoft is committed to providing support for

Dynamics Marketing until October 31st, 2020 in order to honor and facilitate any renewed Enterprise Agreements.

 

Furthermore, we want to highlight a few of the most important points below:

 

  1. If you have purchased Microsoft Dynamics Marketing Enterprise directly through MOSP (web-direct) will be able to continue to use Microsoft Dynamics Marketing for the duration of their agreement.
    If auto renewal is enabled, the renewal of the Dynamics Marketing Enterprise will be automatically taken care of but only until the 31st January 2017.  Customers may also request their subscriptions renewal through Billing & Subscription support until October 31st, 2017.
  2. Customers who have CRM Online Enterprise licenses that include Microsoft Dynamics Marketing can continue using CRM Online and their existing Microsoft Dynamics Marketing instance throughout the license period.
    If auto renewal is enabled, the renewal of CRM Online Enterprise will be automatically taken care of but only until the 31st January 2017. This renewal includes the Dynamics Marketing license.
    For a renewal after this date customers will need to transition the licenses to a Dynamics 365 licensing plan. Microsoft Dynamics Marketing will not be included within the new plan.  In this case, customers who had activated Dynamics Marketing should contact Billing & Subscription support to convert and if needed renew the license for their existing Dynamics Marketing instance. Renewal can be requested Billing & Subscription support until October 31st, 2017.
  3. Customers with an Enterprise Agreement will be able to request renewals based on their individual renewal dates until October 31st, 2017 by working through their assigned Microsoft Solution Sales Professional (SSP) or the Volume Licensing Service Center.

 

In the near future, we will be sharing further details on the new marketing application included with all “Dynamics 365 for Marketing, Business Edition” plans.  Please monitor this website https://blogs.msdn.microsoft.com/crm/ for future updates and details as they become available.

 

 

 

The Microsoft Dynamics Marketing Team

Dynamics 365 app for Outlook is coming soon!

$
0
0

Productivity is everything. Sales people and customer service experts want to achieve more in less time, and focus on getting the job done as efficiently as possible.

Dynamics CRM App for Outlook was first introduced in CRM 2016. Now, I’m proud to announce the next generation of the app—Dynamics 365 App for Outlook, which will be available in the fall release of Microsoft Dynamics 365.

With the new app, you can view Dynamics 365 information about all your email recipients, link an email message to a Dynamics 365 record with one click, and quickly view your most recently used Dynamics 365 records. And you can do all this without leaving your Outlook inbox. Use the Outlook user interface you already know and do it faster than ever!

Composing the same type of email message over and over is a waste of time. Now you can take advantage of Dynamics 365 email templates so you don’t have to enter the same information over and over. When you’re composing an email message, you can also attach knowledge articles or sales literature from Dynamics 365.

But it’s not just about email. Now you can also track Outlook meetings and appointments, and create Dynamics 365 activities, such as phone calls and tasks—all without leaving your inbox.

Last but not least, you can track your Outlook contacts, link them to Dynamics 365 accounts, and keep these contacts completely in sync. Do all this through the new Office add-in—you don’t have to use the old Outlook COM add-in anymore!

The next generation of Dynamics 365 App for Outlook is integrated with Dynamics 365 online, as well as on-premises, whether you use Exchange online or Exchange on premises. It’s supported on Outlook for the desktop, Outlook for Mac, Outlook Web Application, and soon on the Outlook app for iPhone.

Watch this video to learn more about Dynamics 365 App for Outlook.

Dynamics 365 app for Outlook

Update client apps Registration in Active Directory Federation Services (AD FS)

$
0
0

This post applies to Apple iPad, Windows tablets, and Windows phones for On Premises customers, and for Online customers who are using their own federated identity provider

We have updated our mobile applications and added more Redirect URIs. The following updated Powershell command must be run in your AD FS server to register the tablet and phone apps:

Add-AdfsClient -ClientId ce9f9f18-dd0c-473e-b9b2-47812435e20d -Name "Microsoft Dynamics CRM for tablets and phones" -RedirectUri ms-app://s-1-15-2-2572088110-3042588940-2540752943-3284303419-1153817965-2476348055-1136196650/, ms-app://s-1-15-2-1485522525-4007745683-1678507804-3543888355-3439506781-4236676907-2823480090/, ms-app://s-1-15-2-3781685839-595683736-4186486933-3776895550-3781372410-1732083807-672102751/, ms-app://s-1-15-2-3389625500-1882683294-3356428533-41441597-3367762655-213450099-2845559172/, ms-auth-dynamicsxrm://com.microsoft.dynamics,ms-auth-dynamicsxrm://com.microsoft.dynamics.iphone.moca,ms-auth-dynamicsxrm://com.microsoft.dynamics.ipad.good,msauth://code/ms-auth-dynamicsxrm%3A%2F%2Fcom.microsoft.dynamics,msauth://code/ms-auth-dynamicsxrm%3A%2F%2Fcom.microsoft.dynamics.iphone.moca,msauth://code/ms-auth-dynamicsxrm%3A%2F%2Fcom.microsoft.dynamics.ipad.good,msauth://com.microsoft.crm.crmtablet/v%2BXU%2FN%2FCMC1uRVXXA5ol43%2BT75s%3D,msauth://com.microsoft.crm.crmphone/v%2BXU%2FN%2FCMC1uRVXXA5ol43%2BT75s%3D, urn:ietf:wg:oauth:2.0:oob

You will get the following error if you don’t run this updated Powershell command:

AADSTS50011: The reply address ‘[msauth URL]’ does not match the reply addresses configured for the application: ‘{Client app ID, which is a GUID}’. More details: not .

When your users sign in after upgrading their devices, they’ll see this error:

Sorry, but we’re having trouble signing you in. We received a bad request.

White Paper:  Microsoft Dynamics CRM 2016 Service Pack 1 Performance Benchmark on Azure Infrastructure as a Service (IaaS)

$
0
0

On behalf of the Microsoft Dynamics 365 engineering team, I am pleased to announce the release of a white paper, Microsoft Dynamics CRM 2016 Service Pack 1 Performance Benchmark on Azure (IaaS) which is currently available for download, from the Microsoft Download Center. It is one of the publications, as promised in the Dynamics 365 Team blog a few weeks ago.

This whitepaper provides a benchmark for performance of Microsoft Dynamics CRM 2016 SP1 and explains the configuration, topology, optimizations, data profile, and test workload used. It also demonstrates the scalability and performance of Microsoft Dynamics CRM 2016 SP1 on standard “off the shelf” Azure Virtual Machines.  We believe that this whitepaperwill benefit a significant number of enterprises that are still considering or evaluating to migrate their on-premises CRM instances to cloud.

We’d like to recognize the efforts of Matt Brown, Grant Geiszler, Brandon Kelly, Aditya Varma, Matt Peart and the broader CRM Product Group for contributing to and reviewing this paper to help ensure its completeness and accuracy.

We would love to hear your feedback.

Thanks,

Srikumar Nair

Viewing all 455 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>