Archive for the ‘Dynamics 365’ category

Telemetry, A!, Big data analytics are just some of the features that are part of the Azure cloud that are leveraged by Microsoft Dynamics. One example is the Optimisation advisor that can help business users and implementors to adopt best practices to optimize the business processes that they own.

Incorrect configuration and setup of a module can adversely affect the availability of features in Finance and Operations, system performance, and the smooth operation of business processes. The quality of business data (for example, the correctness, completeness, and cleanliness of the data) also affects system performance, and an organization’s decision-making capabilities, productivity, and so on. The Optimization advisor workspace is a tool that lets power users, business analysts, functional consultants, and IT support functions identify issues in module configuration and business data. Optimization advisor suggests best practices for module configuration and identifies business data that is obsolete or incorrect.

Optimization advisor periodically runs a set of best practice rules. A default set of rules is released together with Microsoft Dynamics 365 for Finance and Operations version 8.0 (April 2018). However, users can also create rules that are specific to their customizations, solutions from independent software vendors (ISVs), and business data.

Optimize configuration choices to improve for example the performance of inventory closing, or wave processing, or work creation in the warehouse.

To get the best out of your Dynamics 365 Finance and Operations System contact Synergy Software Systems your Dubai Dynamics Partner (since Ax v2.5 2003) – with over 200 consulting man years of experience in implementing and supporting this solution.
0097143365589

AT the end of 2018 Microsoft announced that the. Azure Kubernetes Service has added the open-source system, Moby, to provision containers and deliver more frequent upstream patches.
Additionally, the team reduced cluster provisioning time, fixed a Stream Watcher error and updated a Linux kernel for a second GitHub problem.

Azure Monitor Logs UX was in preview last year, users can now click on charts and tables in Log Analytics in view the new Logs UX instead, with a new query editor and full schema view.

On January 2, Qatar’s prime minister, H.E. Skeikh Abdullah bin Nasser bin Khalifa Al-Thani opted to help setup a large Azure data center. The prime minister and the Cabinet issued a draft law creating a “Media City” with an independent budget that will host the data center. Microsoft already operates a Content Delivery Network (CDN) in the country, but it has no cloud regions active in the Middle East. That is about to change, though – last year, the company announced that it would open data centers in Dubai and Abu Dhabi in 2019.

Ankabut, the United Arab Emirates’ Advanced National Research and Education Network (NREN) an initiative of Khalifa University, offers academic institutions connectivity to other education networks around the world. It has partnered with Huawei, to launch a cutting-edge new cloud solution in the UAE, Microsoft’s Azure Stack.

This will be the first implementation of Microsoft’s Azure Stack solution in GCC and the ME Region. Through this partnership, Ankabut aims to take the education infrastructure in the UAE to the next level of innovation and intelligibility by implementing the platform that will offer educational institutes cloud-paced innovation and computing management simplicity, cost optimization, higher quality, huge potentials and capabilities, in addition to more reliability and added value services.

(if your idea of surfing is on the beach rather than the internet then try http://azure-beach.com/

Pretty scary.We have suffered catastrophic destruction at the hands of a hacker, last seen as aktv@94.155.49.9 This person has destroyed all data in the US, both primary and backup systems. We are working to recover what data we can.

Though they’re back up and running, who knows if customers will stick by them, or will sue them.
What impact that had on infrastructure mail servers, backup servers, and SQL Servers for customers is hard to judge.
A large number of people might have lost their mailboxes and previously stored mail that was in IMAP storage.
This is likely an annoyance for individuals, but potentially catastrophic for businesses. Imagine your small business hosted with them and all your mailboxes were lost with customer communications and who knows what else.

Could this happen with a cloud provider like Azure O365, Google Apps or AWS?
Maybe but they will have DR backups,
But what if you store back ups on the cloud but run on premise- how long would it take to mass restore multiple, customers? Do you still have ad3qute on premise test systems to restore on and the staff and the time to do it?

Do you assume that you will always have either a primary server and an online backup server/share/bucket/container and can download data.
The problem is that online systems that connect to the primary can be accessed.
If an attacker were to access one, they potentially could access the second.
The world seems to be moving towards more online storage, or in the case of cloud vendors, a reliance on snapshots. That might be good enough for cloud vendors, but is it good enough for your on-premise system.
It’s likely that an attacker, possibly even with insider help, would wipe out backups first, then primary systems.
Some sort of disconnected offline backup of data, especially database servers gives you a third line of defence.
don’t forget that back up- need to be tested- if the back up software compatible with old versions, does your back up use the same version as the current erp software installed on your primary, or the same SQL version (i.e when you upgrade do you also upgrade your back ups, or maintain an older environment?)

Microsoft and other large vendors have had downtime whether self induced by releasing code too early, or due to hardware failure, or malicious attach . What is important to realise is just how infrequent are just issues given the number of clients they have across a range of solutions, and how little was the downtime and how fast they are at in addressing issues that arise. The think about how you would have been able to deal with the same issues in your own server room?

There are increasing risks, and increasing issues of statutory compliance with regard to data protection e.g, GDPR. The cloud generally offers cheap storage nd robust systems, yet it needs to be part of a holistic approach to reduce overall risk and cost, and not the only line of defence.

This release is compatible with Dynamics 365 9.x.
To update to this release, visit the Admin Center for Dynamics 365 online, solutions page to install the update. \

Project Service Automation (v3.3.0.258) Some Improvements
• Timesheets
Weekly time entry with support for customizations. This feature enhances the time entry experience in Project Service Automation by providing the ability for project resources to enter time for the entire week at the same time. It will also be possible for system customizers to customize this view with custom fields or lookups to other entities. Customizers will also be able to implement custom business rules to support their organization’s practices.

• Sales ◦Price list Markups
With this feature, users of PSA price list will be able to create new price list from an existing price list and apply inflationary markups on the different components of the project price list.

◦ • Per unit pricing on Expense categories
With this feature, certain expense categories can be setup with appropriate units and a price and cost per unit using price lists in PSA. This setup will be used to default the per unit rates on all business transactions in PSA such as Quote line details, Contract line details, Project estimates, Expense entries, Journal lines and Invoice line details. This feature opens up scenarios around pricing and costing Mileage, out-sourced work and some unit – based work categories such as processing pay slips, invoices etc. on projects. With this feature, both product-based contract lines and the time and expense actuals have to be marked as “Ready to invoice” before these can be added to a draft invoice in PSA. This feature allows for customizations in the area of PSA’s proforma or invoice proposals. Customers and partners have a way to tailor the creation of draft invoice proposals in PSA by programmatically manipulating the Billing status values on unbilled sales actuals for time, expense, fees and on product-based contract lines.

◦ • Allow user to delete products lines from Project Invoice when the invoice in the draft state.

• Project task form. With this feature, users will be able to access task details directly from the project grid, by selecting the new ‘Edit Task’ schedule grid action. This new form is ideal for extensibility scenarios for tasks, for example: tracking Task Health or Task Type. Users will also be able to easily add notes to a task, encouraging

◦ ◦Full screen toggle- This new UI control enables users to expand the following grid to full screen for an improved editing experience: Schedule, Resource Assignments, Resource Reconciliation, Estimates and Expense Estimates.

Bug Fixes
•Fixed: Restricting the ability to create invoices without approved actuals.
•Fixed: Deleting a contract milestone for an unposted invoice, prevents posting or deleting of the invoice.
•Fixed: Tracking View: Client-side and Server-side calculations are different.
•Fixed: Invalid invoice frequency setup can lead to “Object reference not set to an instance of an object” error when trying to create an invoice schedule.
•Fixed: Project Approval has overlapping command sequence for “Approve” and “Reject” impacting the Ribbon Work Bench.
•Fixed: Null reference exception when creating Project Team Member (and booking resource) through Workflow.
•Fixed: Marking a resource request as complete removes the generic resource from the assigned task when multiple named resources fulfilled the requirement.
•Fixed: Solution Upgrade failures when customer data contains tasks with null dates.

This version will be released in January 2019 and has an actual build number of 8.1.227. It includes platform update 23.

For the many Extensibility changes in Dynamics 365 for Finance and Operations version 8.1.3 see https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/extensibility/extensibility-changes-813

Collection letters
Set up collection letters by customer,, so that the collection letter code for each transaction is tracked, but the collection letter processing is based on a single collection letter level that is stored for the customer.

Settle remainder
To settle the amount remaining from settlement activity by applying that amount to a ledger account or to another customer. Settle the remainder either when you are settling amounts entered into a journal, or when settling open transactions.

GlobalizationElectronic reporting:
• Import from files in JSON format. You can now configure an Electronic reporting (ER) format to parse incoming files in JSON format. You can then set up ER mappings that specify how information from JSON files is used to update application data.
• Support country context-specific ER model mappings. To isolate country-specific logic of data access in a single ER model mapping.
o Specify a country context for ER model mapping.
o Manage multiple country-specific mappings for a single ER data model.
o Depending on the legal entity’s primary address, the appropriate country/region-specific model mapping will be used when an ER format is used to generate an electronic document.

There are also some Russian localisations for AR AP movement registers that may be worth checking.

Platform 23 update features:Legal entity filtering using grid column headers
For grids with cross-company queries, users can filter the Legal entity column using the column drop-down menu, similar to other columns in the grid. A user looking at the global transactions for a specific customer, can find the transactions within a small subset of companies. Prior to this feature, he would have had to filter using the Customer range tab on the Advanced filter or sort dialog box, or utilize page-specific custom filters.

Export to Excel
In Platform update 22, the Export to Excel feature was improved to allow users to export up to 1 million rows from a grid in Finance and Operations, a substantial increase from the previous 10,000-row limit. In Platform update 23, after the export completes, users will receive a notification in the Action center that the export has finished. The notification includes a link to download the Excel file containing the exported data. The link and notification are accessible for approximately three days after the export completes.
Manage access to network printers across legal entities
System network printers management form. System Administrators can use this, along with the Document Routing Agent (DRA) to register network printers with Dynamics 365 for Finance and Operations. When you enable this feature, a Preview link will appear on the System network printers form (Organization administration > Setup > Network printers and click System network printers). After you register the network printers with the service using the DRA, you will see the configuration information for each legal entity in the organization.

Enabling index hints in X++
Microsoft Dynamics AX 2009 and earlier versions supported INDEX HINTS from X++. However, this was deprecated when Dynamics AX 2012 was released. A reason why this was deprecated is because a misguided index hit could damage the queries. However, thousands of queries in hundreds of tenants shows that SQL may come up with less optimal plans for simple queries, Finance and Operations has thus brought back X++ hints. However, X++ hints should still only be used with extreme caution. Use Index hints sparingly, and only when you can ensure that it causes more benefit than harm. When in doubt, avoid using index hints. A new API is added on common allowIndexHint with a default behavior of False. This allows developers to opt-in and explicitly enable index hint. The old syntax on the select statement for specifying index hint is reused.For an existing X++ code that specifies index hint, there is no change to the current behavior until the new API is invoked.

Automated refresh of Entity store (opt-in)
Let the system manage Entity store refresh instead of scheduling the refresh yourself. When enabled, choose a refresh pattern (hourly, twice a day, daily, or weekly). When specified, the system keeps the entity store updated for the selected pattern. The system will also switch to the new update form, where you will be notified with a status and possible refresh issues.

Entity store as a Data Lake (preview)
In Platform update 23, you can select to use Entity store as a Data Lake. When this feature is turned on, Entity store data isn’t populated in the relational Entity store database in the Microsoft subscription. Instead, it’s populated in an Azure Data Lake Storage Gen2 account in your own subscription. You can use the full capabilities of PowerBI.com and other Azure tools to work with Entity store.

For more information: contact Synergy Software Systems, Dubai based since 1991 and Dynamics Partner since 2003.
0097143365589

Enhancements
• Numerous performance improvements.
• Improved Sitemap: Improved the Field Service app module sitemap including Connected Field Service entities.
• Field Service SLA: Implemented SLA for Work Orders which connects the long-standing SLA functionality to the Work Order Time From Promised and Time To Promised fields ensuring that arrival time related SLA fulfillment is driven by existing Field Service scheduling tools.
Note: Out of the box, SLA is not enabled on the Work Order entity. Enable it to use the two SLA KPIs that are shipped as part of the solution.

Fixed: Upgrade Bug – Booking is updated with groupId before the record is created.

Connected Field Service enhancements

Connected Field Service (CFS) and the IoT solution, now deploys with Field Service. The CFS solution extends Field Service to cater to IoT device-driven scenarios so that organizations can respond to device anomalies and react. This allows customers to predict issues in advance and fix issues remotely or schedule a service visit, preventing failures in a proactive way.

• The CFS solution is now available out of the box with Field Services, which eliminates the need to separately install the additional solution package.
• The sitemap for the Field Service app module now includes the CFS entities as part of the default navigation. The IoT settings in the navigation are now merged with the settings section of Field Services.
Note: Non-System Administrators may need to include additional permissions for the CFS entities to see the CFS entities.
• The CFS deployment app for PaaS customers (with Azure IoT Hub) is re-architected for improved performance during initial setup. The user experience for deployment process is also updated to provide better deployment experience for administrators.

Technician Productivity

• New Field Service Mobile app: The new mobile application that brings with it a plethora of new features. See https://aka.ms/fsmobile-docs for more information.
• Push Notifications: Send push notifications to the new Field Service Mobile application based on any conditions. Create a workflow and select the Field Service Mobile Entity Push Notification workflow action to use this feature.
• The out-of-the-box example workflow will allow bookable resources to be notified when they are booked on a work order.
• Geofencing: Enable geofencing so that when a booking is scheduled for a work order, a geofence gets created around the service account for that work order and any exit or entry of that geofence by a bookable resource can generate a geofence event record. Out-of-the-box workflows are provided that can perform actions based on these geofence events such as sending a push notification to a bookable resource’s Field Service Mobile app when that resource arrives on-site for a work order.

“All customers must be on the latest version of Finance and Operations by April 30, 2019.”

That is getting very close if you are sitting on a legacy v7 or 7.3 version.
There is an additional challenge if you have customised code or an ISV add on that still uses layered code then that will need to be rewritten using extensions.

For cloud deployments Microsoft does most of the heavy lifting for you. However, it might not be that simple especially for DEV?BUILD and TEST evnironments. When the environment has other non-Microsoft packages installed, LCS will prevent you from simply applying the update package. You may have some ISV-solutions or some package you’ve created and released, and then installed on the environment, through LCS. When you try apply the update package, LCS will stop you, and list the non-Microsoft packages installed. packages blocking you.

However, for on-premise deployments: “The customer is in full control of its on-premises deployments and must follow this policy. The customer is in control of installing updates in its on-premises environments”

So there is rather more work to do.
You may also need to consider expiring certificates.

Dynamics 365 for Finance and Operations version 8.1 is the latest major release before Microsoft will move over to the “OneVersion” strategy. From April 2019 onwards all D365FO customers will be migrated to the latest version (v10 release is planned for april 2019), and will kept updated to the latest version thereafter.

It is therefore very important to upgrade to the 8.1 release for all customers running an older version of D365FO. An important reason is that Microsoft has guaranteed that the move to 10 will be only supported form version 8.1 So make sure that you are on this version before April 2019.

There is limited time and skilled resource available, so if you have not already put plans in place then don’t delay.

For expert assistance to upgrade your Ax7/D365 environment call us on 00907143365589.

If you did not self-schedule this update by last August, Microsoft will force an upgrade for anyone on Microsoft Dynamics Version 8.2 or earlier.

As of February 1, 2019, Microsoft will no longer support any of their customers that did not complete the upgrade to the newest version.

The size, cost, and scope of upgrading your Microsoft Dynamics environment to the supported version depends on the complexity of the customizations. Microsoft does not require third-party add-ons to continue to support the add-on in the future, meaning third-party apps in your account may not be compatible with the January 2019 upgrade.

Custom development that was applied to your Microsoft Dynamics instance should be checked for compatibility with the upgrade in a separate environment. Some and maybe all of your customizations may have to be re-implemented in your environment to comply with the upgrade. Time to analyse develop, test, deploy etc is running out.

On-premise Microsoft 365 users are not currently up against a deadline for upgrade–but it is certainly a possibility in the future.
.

Upgrade is not trivial especially when you have lots of customisations and bespoke reports and interfaces. Plan plenty of time for conversion and for testing and contingency. There is backlog of companies who need to migrate and only a limited number of skilled consultant available.

Decide as soon as possible whether on-premise or on cloud. If on-premise then consider what extra hardware you will need and whether you also need to upgrade SQL server. Don’t forget that SQL license costs have also changed.

It is not too early to start budgeting – find out what you get and don’t get on the cloud, there are both hidden costs, (e.g. extra back up storage space) and hidden savings (e.g. electricity). What extra environments or storage will you need e.g for dev and test over those used by Microsoft. How have license types and costs changed, understand the Modern Lifecycle Support update policy, .

Dynamics AX 2009 Service Pack 1 (SP1), Dynamics AX 2012, and Dynamics AX 2012 R2:
Mainstream support fends on October 9, 2018 after that date, only security hotfixes will be provided for these three versions through the extended support period that continues until October 12, 2021.

Dynamics AX 2012 R3
Mainstream support for continues through October 12, 2021. Microsoft will provide security hotfixes, non-security hotfixes, and regulatory updates for Dynamics AX 2012 R3 throughout that mainstream support period. The source code for these non-binary, non-security hotfixes and regulatory updates will continue to be available for customers active on the Enhancement Plan or Software Assurance.

Can customers on Premier Extended Hotfix Support or on Unified Support Advanced and Performance Levels get a non-security hotfix or regulatory update?

No. Neither non-security hotfixes nor regulatory updates will be available for Dynamics AX 2009 SP1, Dynamics AX 2012, or Dynamics AX 2012 R2 during the Extended Support phase of the product lifecycle.

While the ability to request a non-security hotfix for select products is included with Unified Support Advanced and Performance Levels, Microsoft has determined that non-security hotfixes cannot be provided with a commercially reasonable effort for these products. As a result, no requests for non-security hotfixes or regulatory updates will be accepted.

However, Microsoft will continue making security hotfixes, non-security hotfixes, and regulatory updates for Dynamics AX 2012 R3 throughout that mainstream support period. The source code for these non-binary, non-security hotfixes and regulatory updates will continue to be available for customers, and their partners, active on the Enhancement Plan or Software Assurance. Dynamics AX 2009 SP1, Dynamics AX 2012, and Dynamics AX 2012 R2 customers can selectively integrate those changes as required. Customers and partners can get the source code from packages attached to relevant Dynamics AX 2012 R3 KB articles published on LCS and discoverable through LCS Issue Search.

Will I still get a regulatory update for Dynamics AX 2009 Service Pack 1, Dynamics AX 2012, and Dynamics AX 2012 R2?

No, Microsft will only provide regulatory updates for Dynamics AX 2009 Service Pack 1, Dynamics AX 2012, and Dynamics AX 2012 R2 for regulatory changes with the law enforcement dates on or earlier than October 9, 2018.

What happens if a new bug is found by a customer in Dynamics AX 2009 Service Pack 1, Dynamics AX 2012, or Dynamics AX 2012 R2?

The bug must be reproducible in Dynamics AX 2012 R3. If it is reproducible and accepted, then a hotfix will be provided for Dynamics AX 2012 R3 and the customers can elect to integrate this hotfix in their version themselves, or work with their partners to integrate the changes.

An all-in-one business management solution that helps your business connect financials, sales, service and operations.

Business Central for SME Companies
Many businesses start on small, low-featured finance packages due to the low cost and ease of use. However, as the business grows you will start to suffer from:
• Limited or no functionality for managing areas of your business
• Lack of intuitive reporting
• No integration between departments

If you started with a basic finance package and need something more to run your business, then Dynamics 365 Business Central could be the solution for you.
• Familiar Microsoft look and feel for ease of learning and use
• Implement just the areas that you need to use
• Security and Permissions based on job roles

If you use an external accountant, then the good news is that Business Central comes complete with a free accountant license., which gives access to just the areas of the system they need to manager your finances.
Manually inputting data into spreadsheets is both timely and open to a lot of risks. Reporting is also very limited and often the data is disparate between work books. Building new areas of the business can be complex and requires huge amount of management time to create the processes.
Business Central comes with in-built functionality for every area of business, all integrated with a centralised chart of accounts. This means that you only enter the data once and can spend time focused on strategy based on meaningful insights from the in-built reporting and integrated Power BI.

There many tasks to be done for the Fiscal year-end closing process.
Those include task for all functions not just finance.
For over 10 years Synergy has conducted Year end training courses to help prepare Dynamics users for their fiscal close.
Our 2 day workshop encompasses:
Key tasks and sequence
Tips and trick
Key reports,
Use of MR and Power Bi
Sales, Supply chain, HR, IT tasks
Hands on practice
The course content applies to almost all versions and will be run in Dynamics Ax 2012 R3. it will however will also introduce the Dynamics 365 Financial closing workspace.

In October 2018, Microsoft adjusted the configuration of the Finance and Operations Develop and Test environments for better performance. All new deployments have moved to Managed premium disks, optimized for DS12v2 VMs. because of updates to code and metadata, development and testing requires extensive disk access operations. Memory optimized VM sizes offer a high memory-to-CPU ratio that are best for relational database servers, with medium to large caches, and in-memory analytics. The M series is the highest spec.

(The Dv2-series is a follow-on to the original D-series, and features a more powerful CPU. The Dv2-series CPU is about 35% faster than the D-series CPU. It is based on the latest generation 2.4 GHz Intel Xeon® E5-2673 v3 2.4 GHz (Haswell) or E5-2673 v4 2.3 GHz (Broadwell) processors, and with the Intel Turbo Boost Technology 2.0, can go up to 3.1 GHz. The Dv2-series has the same memory and disk configurations as the D-series. Moving to Managed premium disks will provide a much better performance experience for these operations.)

Synergy recommends that you deallocate, delete, and re-deploy new Develop and Test environments to take advantage of this new topology. Before you delete your Development or Test environment, make sure that you save all of your work, check your code into Azure DevOps (formerly known as VSTS), and make a local backup of any test database that you would like to preserve.

Allow up to 48 hours for a redeployment request to be processed by Microsoft.

If you are running Microsoft Dynamics 365 for Finance and Operations and you are on version 7.3 or below, then be aware that the product will be considered as end of service after March 31, 2019. Note however that other Dynamics 365 Apps are also impacted e.g. Customer Engagement and Field Service.

From April 2019, all Microsoft Dynamics 365 customers for all Dynamics solutions, will run on the same version and code base. This means from Microsoft point of view that it is still possible to have own customizations and ISV solutions in your own environment. The standard application will be the same for all customers.

As of April 2019, the product version number will be 10.0. From then expect major releases every April and October.
In between there will be continuous updates for platform, application and financial reporting fixes as well as smaller functional features and regulatory requirements. Version number ‘9’ will be skipped for Finance and Operations. Customer engagement is on version 9 so to have a single product range on the same vision, Microsoft has to align the version numbering to be the same across all of the Dynamics apps.

The service will also end for version 8.0. We advise to move to version 8.1 as soon as possible. If you are already on version 8.1, then you are already enrolled in the continuous update plan. The 10.0 version will then be an update when coming from this latest version; not an upgrade.

If you are running on version 7.3, then in general you also have to be on version 10.0 starting April 2019. If you have submitted extension requests, then you are expected to have no issues for upgrading and your 7.3 environment will be considered as end of service starting April 2019. That also means you need to move all over-layered coding into extensions. If you use an ISV module then check with the ISV vendor whether is ahs issues with over-layered code to resolve.

There is limited time to prepare and test, (and limited D365 technical skills, in the market to move all customers at the last minute, and it does not happen in a day.) Starting with the April 2019 update, you can validate major updates in a sandbox environment in advance of the update release. This will help you assess productivity and efficiency gains of the new capabilities, as well as train your end users about new capabilities

It’s important to do this sooner than later. The move from 7.3 is a significant exercise i.e. it’s an upgrade. Thereafter the advantage of the new platform is that in future it will be updates. The ongoing April and October updates will be backward compatible.

There are many enhancements both technical, and functional in 8.0/B.1. So plan time for some additional end user training and testing days.

Synergy has completed the upgrade, and also upgraded its D365 Payroll and HR admin modules for this new release and for the latest kernel..

Note: All customers must be on the latest version of Finance and Operations by April 30, 2019. However, Microsoft will make an exception for customers who have unfulfilled extension requests that have been submitted to Microsoft. Those customers can be on version 7.3 until April 2020.

In November 2018, all ACS components were permanently shut down. This affects all requests to the service i.e. those fail. This includes the Access Control management portal, the management service, secure token service, and token transformation engine rule. Microsoft made changes to Azure Service Bus that affect Microsoft Dynamics AX 2012 Azure connector, and impact email workflow approvals, companion/mobile applications, and vendor portals. It also affects any other application or service that uses Access Control Service (ACS).

If for example you use Dynamics AX 2012 mobile or tablet applications for time and expense management, and/or approve workflows via email, then be aware of the changes to Azure Service Bus. The Microsoft Dynamics AX 2012 Azure connector uses the Access Control Service (ACS) for user authentication. The management of authorization rules is managed inside by the Azure Active Directory Access Control Service (ACS), and the tokens obtained from ACS are then passed to Service Bus to authorize access to functionality in AX.

ACS is now replaced by Shared Access Signature (SAS) token authorization model. A shared access signature (SAS) provides you with a way to grant limited access to objects in your storage account to other clients, without exposing your account key. A shared access signature provides delegated access to resources in your storage account. With a SAS, you can grant clients access to resources in your storage account, without sharing your account keys. This is the key point of using shared access signatures in your applications–a SAS is a secure way to share your storage resources without compromising your account keys.

To continue using email workflow approvals, mobile applications, and other Dynamics AX features, if you have nit already done so then you will need to migrate your components previously using Access Control Service (ACS) to Shared Access Signatures (SAS). This token model is provided directly by Service Bus and can be used without any intermediaries through access to the SAS rule name and rule key.

Synergy is a well established, solution provider across the Middle East region.
Synergy has a strong presence in several key verticals; Manufacturing, Construction, Hospitality Insurance, Financial Services, Government. Media, Oil and Gas, Distribution.
Synergy is particularly well known as a Gold Partner of both Infor Sunsystems, and Microsoft Dynamics Ax and for its implementation expertise and exceptional support. It is based centrally in Dubai in the Karama district since it was registered in 1991, and occupies a 7,000 sq ft office with around 80 full time employees.