Workflow Approvals are now compatible with SAS – Azure ACS retirement update


Workflow Approvals are now compatible with SAS

*NEW update for extensions: https://blogs.technet.microsoft.com/dynamicsaxse/2018/10/09/october-2018-acs-update-extension-available-until-feb-4-2019/

Our mobile apps page has been updated to reflect that any customer using workflow approvals only with ACS can now migrate off of ACS and uptake SAS.  

This migration will require a new version of the mobile connector which is not backwards compatible with ACS. Do not move to the new connector if you are still using mobile Timesheet or mobile Expense.

It is recommended you configure this in a new standalone environment first, and then schedule downtime to uninstall the previous connector and reconfigure to the new version in production.

Steps are documented in the Workflow Approval via Email whitepaper. These steps apply to both R2 and R3.
https://www.microsoft.com/en-us/download/details.aspx?id=37002

 The updated connector (8.2.384) is available for download from the mobile apps page or directly from the link below.
https://mbs.microsoft.com/files/customer/AX/Downloads/productreleases/AXConnectorForMobileApplications.zip

We are continuing to work on publishing the final solution for timesheet and expense.
The final solution is in progress and will be available soon. That final solution will include the updated mobile connector, updated apps for Android and IOS, and the documentation required for the configuration using SAS.

Please be aware that the new solution for timesheet and expense will have a new dependency on ADFS 3.0 rather than ADFS 2.0.

Comments (10)

  1. Dukroz says:

    Will the new solution for timesheet and expense still be compatible with ADFS 2.0?

    1. It will not as mentioned on the last line of this blog.
      “will have a new dependency on ADFS 3.0”

      1. Dukroz says:

        This means that once the new solution for timesheet and expense will be released we (users of ADFS 2.0) will require to upgrade ADFS to 3.0 and then upgrade the mobile connector to SAS? Is there a way for us to prepare for this or any other way that would avoid us from having to upgrade ADFS?

  2. ggoulf says:

    HI Ryan,
    there is an updated documentation ? Because on the doc, you write :
    2 Complete the steps to configure AD FS for authentication.
    3 Complete the steps to update the relying party federation metadata.

    But I Don’t understood how to update the relying party federation, since on the document, the link is to the ACS URL?
    Thanks

  3. ggoulf says:

    Hi Ryan,

    you can ignore my previous comment, I found the solution.

    Thanks

  4. R. Grubb says:

    Ryan,

    We have installed v8.2.384.0 of the connector. We are using this only for Email Approval Services and had been using ACS. After installing the new connector, I noticed there are a number of new parameters as follows:

    ADFDS URL
    ADFS Metadata
    Enable AAD Authentication
    Web Resource URL
    App registration NativeApp ID
    Support Email

    Can you please clarify what is expected for each of these items since it is not in the documentation? Also, previously we were using on ACS, no ADFS or AAD. Are we going to have to use one of these now?

    Thanks,
    Ranny Grubb

    1. Randy – tracking down the answer from the developer that worked on these updates/changes.

    2. Answers from R&D:
      ADFS URL
      – This is an existing parameter and for workflow approval via email feature they should continue to use the values mentioned in the earlier version of rapid start connector.
      ADFS Metadata
      – Has a default value but is not needed/ won’t be used for workflow approval via email feature
      Enable AAD Authentication
      – Defaulted to false, should not be turned on for workflow approval via email feature
      Web Resource URL
      – Has a default value but is not needed/ won’t be used for workflow approval via email feature
      App registration NativeApp ID
      – Has a default value but is not needed/ won’t be used for workflow approval via email feature
      Support Email
      – This is an existing parameter where customer can define their support email so that it gets displayed in the apps for assistance.

      1. R. Grubb says:

        Thanks Ryan. I was able to get it working.

Skip to main content