In case you have multiple applications running on a server (compiled in version supporting TLS 1.2) you can do registry edit to enforce all applications on server to utilize highest possible version. Be careful with this fix as it might cause negative impacts on other applications.

After taking over ADX Portal Microsoft stopped selling it for on-premise version of Dynamics CRM and only licensed Online version of Microsoft Portals. With this move many of the new Dynamics 365/CRM projects which required a portal on top of Dynamics 365/CRM backend had no possible alternative available in market.

Few months back Microsoft announced that there will be a one time drop of source code for Microsoft Portals which would be available for clients/SI looking for a on premise version to use in their projects.

After a long wait yesterday Microsoft released opensource version of Dynamics 365 Portal.

This can be used to automate the process for which we typically required Office 365 Global Admin to Log in to Admin Center and manually slog.

With help of this now we can now go ahead and fulfill our ALM and CI dreams right from setting up a new instance (and going ahead with deploying solutions to those instances using Dynamics CRM metadata calls).

Certain key processes which can be automated through Online Management API are:

Creating a new Dynamics 365 Instance

Retrieving Instance as well as Information about instances

Deleting an Instance

Taking a Backup (of instance)

Retrieving Backup

Restoring Backup

Retrieving the Templates i.e. Sales, Customer Service, Field Service etc…

Retrieve Currency, Languages supported by Instance.

Retrieve operation statuses (which have been Triggered)

Update Admin Mode setting of instance so that its not available to users.

Along with above Online management api can also be used to manage server to server authentication by supporting:

Creations of Tenant Application Identity

Retrieval of Tenant Application Identity

Enable or Disable Tenant Application Identity.

Key points to note for API:

User must have either Global Admin or Service Admin privileges in Office 365 tenant.

While working on Dynamics CRM one of the most irritating issue is that System Views are Global and there is no (direct?) way through which you can control them based on User/Security Role/ BU etc…

Till now I have come across 3 different ways you can restrict system views visible to users and you can select which method to use for your need:

1. Using Security role based Views:
This is not an official way of controlling system views but its more or less supported.
For this method there is a tool (which used to be free) called Role Based Views by CRM MVP Debajit Dutta.
You can download free version at codeplex which is available for 2011 and 2013.
For 2015 onwards you can purchase it at XRMForYou.

In principal how this tool works is.
It has plugin written on Retrieve Multiple (of savedquery) and based on configuration you do in the tool, it intercepts the retrieve multiple, checks user security role and decides whether to let user see the view or not.

2. If requirement is not role based and its to hide certain views which were created specifically for Sub-grids.
In few cases we create some system views to display on form sub-grid only, if you want to hide those views in Home screen then simple workaround it “DEACTIVATE” those views.
You will still be able to use those on sub-grid and those will not be visible on home screen and dashboards.
Thanks to OldCat65 for this.

3. You need role based view but don’t want to pay for it.
Option 1: Write your own.
Option 2: Use Apps in Dynamics 365.
Using “Apps” in Dynamics 365 you can create your own site map navigation and define which entities, forms and views are part of app. On the home screen of the App only the views selected within app will be visible.
Bonus, Apps can be restricted based Security Roles.