Alex Chandiwana is a Microsoft MVP, Solution Designer based in the United Kingdom, Passionate about Microsoft Dynamics 365 CE and Microsoft Power Platform . A great believer in helping others to embark on the Tech journey and where needed support their journey. Making Dreams a REALITY through learning #MSDyn365 #Customer Engagement #Financials #Operations #Information #Best Industry Practices #community #learn #powerplatform
Dynamics 365 Pre Go-Live Checklist
A Colleague from Microsoft shared their Pre go-live checklist that is used in their Fast-Track program.
So here is a copy for you all, and what customers must be prepared to answer before Microsoft is deploying the production environment.
1.Solution acceptance by
A.Is UAT completed
successfully? How many users participated in UAT?
B.Did UAT test cases cover
entire scope of requirements planned for go-live?
C.How many bugs/issues from
UAT are still open?
D.Any of the open
bugs/issues a showstopper for go-live?
E.Was UAT done using
A.Business has signed off
after UAT that the solution meets business needs?
B.Solution adheres to any
company/industry specific compliance (where necessary)
C.Training is complete
D.All features going live
are documented, approved and signed off by customer
A.How was the performance
in UAT? Is it acceptable for go-live?
B.If Performance testing
was done, then are there any open actions from it?
4.User & Security
A.How many security roles
are being used. All security roles are setup and tested?
B.Users that will need
access at go-live have been setup with correct security role?
A.Data migration status –
Masters & Open Transactions/Balances
B.Business has identified
owners for data validation?
C.Review cut-over plan:
Business & Partner teams are comfortable with the plan?
D.Does the Data migration
performance fits within cut-over window?
A.Are the configurations
updated in Golden Configuration environment based on changes in UAT?
identified and process in place for post go-live changes in
C.All Legal Entities
configured for Go-Live?
A.Review list of
integrations and readiness plan for each
B.Latency requirements and
performance criteria are met
C.Integration support is in
place with named contacts/owners
fixes/maintenance process defined?
B.Code promotion (between
environments) process is in place, documented and the entire team knows and
understands the process
C.Code promotion schedule
for production is in place?
D.Emergency process for
code promotion to production is defined?
9.Monitoring and Microsoft
A.LCS diagnostics setup and
knowledge transfer to customer
B.Issue resolution and
Escalation process defined – LCS support is verified?
Microsoft in recent months made available a much requested feature by many with the additional way to access read-only data in Microsoft Dataverse. The TDS endpoint for Microsoft Dataverse allows read-only access to Dataverse for reporting and analytics requirements. The Tabular Data Stream (TDS) Protocol endpoint functionality is managed by an administrator with access to the Admin center. This feature becomes a game changer as many Microsoft customers who required this feature and often went down the root of the Data Export Service can now start exploring this capability Prerequisites: To get started using this feature, you will need to ensure that TDS endpoint is enabled as this is required to be able to use this feature via Power BI or SSMS. Sign into the Power Platform Admin Center :( https://admin.powerplatform.microsoft.com/environments ), and then select the appropriate sandbox environment. Note: Its always good practice to test new features in a Sandbox Environment Validate t
Overview. Dynamics 365 CE provides functionality to automate business processes in the background or on a click of a button requiring a user to initiate this automation. In this blog post the scenario is focused on an issue a user may experience while using dynamics 365 CE on automation which is initiated by a user looking to use an On Demand. This automation triggered by a user is called an on-demand workflow. Problem When a user goes into Dynamics 365, they are unable to see or run a workflow/flow which may have been created. So how do you resolve this issue? Steps to Resolve System Settings 1.a) Login into the Power Platform Admin center ( https://admin.powerplatform.microsoft.com/environments ) and Select your Environment name > Settings > Behavior . At this point validate that the " Show Power Automate on forms and in the site map " is toggled 1. b) Validate that the setting, you will need to navigate to Settings > Administration > System Settings >
Purpose The purpose of this post is to set out the direction, steps,scope, and implementation approach for the Dynamics Outlook App configuration item Audience This post is intended for Technical Teams/Administrators looking to implement the Dynamics Outlook App for On-premise environments. Pre-Requisites Dynamics 365 with IFD Configuration Dynamics 365 Update 18.104.22.168 (KB4046795) Minimum ADFS requirement ADFS 3 upwards due to OAuth endpoint Minimum Exchange 2016 or 2013 with Cumulative Update 14 or later Office 2016 *Recommended, Office 2013 *Compatible Supported browsers for Outlook on the web Dynamics 365 App for Outlook can be used with Outlook on the web on the following browsers: Internet Explorer 10, Internet Explorer 11, or Microsoft Edge The following configuration is supported: Protected Mode is enabled for Internet security zone. To enable Protected Mode: in IE 10 or 11, go to Tools > Internet options > Security tab > Internet. Protected Mode