Microsoft Azure Cloud – Can it be trusted

Considering moving your Dynamics GP or Dynamics AX application to the Microsoft Azure Cloud platform but wondering if your data will be safe and meet your industry’s compliance requirements?

A great source of information on these topics is available at the Microsoft Azure Trust Center website ( This site is loaded with material on all aspects of security and privacy with regards to using the Azure Cloud product offering.  The website is broken into five major sections:

  1. Azure’s embedded security and privacy model: It all starts here. Building security into the product from the start as opposed to a bolt-on after the fact. Learn about Microsoft’s Security Development Lifecycle (SDL), Operational Security Assurance (OSA) process, and Privacy by Design in this section of the site.
  2. Security: Keeping your data safe: Security is not just simply encryption. It is also about processes and procedures such as threat management, mitigation, and penetration testing. What value is encrypted data if you can’t access it? Read about Microsoft’s approach in this section.
  3. Privacy: Own and control your data: Microsoft vigorously defends your right to privacy protection demonstrated by their recent win of a major case in the United States Court of Appeals. The ruling prevented the U.S. government from requiring Microsoft to give them access to emails held in a foreign country. Read about Microsoft’s approach and over 20 years of commitment to privacy in this comprehensive section on the subject.
  4. Transparency: Know how your data is stored, accessed and secured: Critics say that CLOUD stands for Cannot Locate Our Users Data.  Microsoft has done their homework with this platform and is ready to earn your trust in this regard.  This section of the site describes Microsoft’s policies and procedures with regards to where your data is stored and how it is secured.  Are you a Canadian company that requires all data to be stored within the country? Learn how to specify that your data remain in the new Toronto or Québec City data center.
  5. Compliance: Conforming to global standards: It is one thing for Microsoft to assert your data is safe and secure but your motto should always be “trust but verify”. This section of the site details the international and industry standards met by Azure and the third-party audits required to verify those standards. It has a very easy navigation tool to enable you to focus on compliance that is relevant to your industry. In the Healthcare industry? Select Healthcare in the drop down box and learn how Azure can meet HIPAA/HITECH requirements.

Still have questions or concerns about leveraging Azure for your Dynamics GP or AX environment?  Consultants with Tridea’s Cloud Business Services practice are available to help you find the right solution to meet your needs.

Microsoft Dynamics GP 2016 Feature of the Day – Import/Export SmartLists from Designer

Enjoy your Microsoft Dynamics GP 2016 Feature of the Day!

Import/Export SmartLists from Designer

GP 2016







Feature of the Day Program

In addition to educating everyone on new features, the Feature of the Day is also meant to evangelize the tremendous features and functionality available in the Microsoft Dynamics GP product. 

Microsoft Dynamics GP: Removing Project Segments

Depending on your company’s requirements, it is often needed to track additional types of data for financial reporting. Many times, segments in the general ledger account structure are used to facilitate this requirement.  With Microsoft Dynamics GP, there are ways to accomplish this outside of the COA, even if it has already been configured to include those segments!  Analytical Accounting (AA) is a very powerful tool that allows additional codes to be added (required or optional) for any amounts hitting specific GL accounts.

The steps to do this are as follows. A historical company database should be created to maintain the data from before any changes have occurred.  Historical balances for net changes (per year, month, week, etc…) should be exported into Excel. This will be used to re-map these amounts into the Analytical Accounting Codes.

Next, the PSTL tool to update the COA will be used to remove the un-needed segments. Analytical account will then be activated and configured. The new GL accounts will be assigned to Analytical Accounting Classes that will dictate whether AA codes are required, optional or not allowed. There are two main ways of bringing over the AA cutover data (that used to be in the GL). The first option is to use the Edit Analysis window to update Journal Entry numbers with AA codes.  This option allows all detailed entries to be converted.  The second option is to bring the net changes per period (year, month, week) using GL entries that are a wash.  For instance, the AA code will be setup as optional (thus not requiring a code to be entered on both sides of the entry.  The entry will be created as a debit and credit to the same account, BUT, the AA code information will only be entered on the appropriate side of the entry.

Testing and changes to Management Reporter may be needed (and are recommended) to complete this conversion process. As always, if any further details need clarification – please contact us!

This article was written by Kaydee Baker, Practice Manager for Tridea Partners. Tridea is a leading Microsoft Dynamics provider.

Microsoft Dynamics GP 2016 Feature of the Day – AA User Access Settings

Enjoy your Microsoft Dynamics GP 2016 Feature of the Day!

Dynamics GP 2016








Feature of the Day Program

In addition to educating everyone on new features, the Feature of the Day is also meant to evangelize the tremendous features and functionality available in the Microsoft Dynamics GP product.