Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
February 2015
www.microsoft.com/dynamics/ax
Table of Contents
Introduction ................................................................................................ 3
Prerequisites............................................................................................... 4
Create a new Windows Azure Service Bus namespace with a companion
ACS namespace ........................................................................................... 5
Configure an Active Directory Federation Service for authentication .......... 6
1.
2.
3.
4.
5.
6.
Introduction
This paper describes how to configure an environment that is running Microsoft Dynamics AX 2012, so
that users can use the Microsoft Dynamics AX companion apps. For a list of the companion apps that
are available, see http://go.microsoft.com/fwlink/?LinkId=335790.
In order for the companion apps to interact with Microsoft Dynamics AX 2012, you must configure the
following components:
Active Directory Federation Services (AD FS) AD FS works with an organizations instance of
Active Directory Domain Services to authenticate users of the mobile phone application. Users are
authenticated based on credentials that are sent by the mobile phone application. Upon successful
authentication, AD FS returns a token to the mobile phone application.
NOTE: If you are using Windows Server 2008, you must download and install the AD FS 2.0 software
to deploy your AD FS server infrastructure. However, if you are using Windows Server 2012 R2, you
can install the AD FS server role using Server Manager. Server Manager provides improved AD FS
configuration wizard pages that perform server validation checks before you continue with the AD FS
server role installation and will automatically list and install all the services that AD FS depends on
during the AD FS server role installation.
Companion app The companion app allows a user to capture a transaction. It then authenticates
the user and sends the message.
Windows Azure Active Directory Access Control (also known as Access Control Service or
ACS) A Windows Azure Service Bus, which is an ACS managed namespace, enables the companion
app to send a message to Microsoft Dynamics AX (which resides on-premises). ACS provides the
authentication that is necessary to send a message via the Service Bus service.
Microsoft Dynamics AX Connector for Mobile Applications The connector listens for messages
sent via the Service Bus, authenticates the sender of the message, and then sends the message to the
Microsoft Dynamics AX 2012 instance.
Microsoft Dynamics AX 2012 The Microsoft Dynamics AX 2012 instance receives messages
originally sent from the companion application. It stores the messages as transactions that are
available to the user (for example, the user will see expense transactions that are captured via the
users mobile phone in the Dynamics AX system).
For information about configuring specific companion apps, refer to the appendix of this white paper.
3
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
The following diagram shows these components and the flows among them.
Figure 1: Required Microsoft components and configurations for Microsoft Dynamics AX mobile apps
Prerequisites
Before you can configure the Microsoft Dynamics AX environment for companion apps, you must
complete the following prerequisites:
Set up and configure the Active Directory server:
The Active Directory server and domain controller should have been set up during the
installation and configuration of Microsoft Dynamics AX 2012.
Install Active Directory Federation Services. You can download the Active Directory
Federation Services 2.0 RTW from http://www.microsoft.com/enus/download/details.aspx?id=10909.
4
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
3. When you are prompted for your credentials, enter your credentials for your Azure
subscription.
4. In the PowerShell command prompt, enter the following command to add a new service bus
service namespace with a companion ACS namespace:
New-AzureSBNamespace name InsertNameHere location InsertRegionHere
Property
Description
-name
-location
5. If you followed the steps correctly and there were no errors, the following information is
displayed.
Name:
Region:
DefaultKey:
Status:
CreatedAt:
AcsManagementEndpoint:
ServiceBusEndpoint:
ConnectionString:
[Name]
[Region]
2pRUX4K5EhE5XKvDsaS+816/Nrqzztkgur/CKsib40w=
Active
8/26/2014 7:24:31 PM
https://name-sb.accesscontrol.windows.net/
https://name.servicebus.windows.net/
Endpoint=sb://SBName.servicebus.windows.net/;SharedSecretIssuer=own
er;SharedSecretValue=2pRUX4K5EhE5XKvDsaS+816/Nrqzztkgur/CKsib40w=
6. Copy the DefaultKey, ServiceBusEndpoint, and ConnectionString for reference later. You will
use the 256-bit secret default key when you configure the Microsoft Dynamics AX Connector
for Mobile Applications service that is deployed on the server. For more details, see
Configuring the on-premises server for Companion apps.
5
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
6
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
5) In the Endpoints list, ensure that the three endpoints in the Metadata section are enabled, as
shown in the following screen shot.
7
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
You can see the list of certificates by clicking Certificates under the Services node in the left
navigation pane of the AD FS 2.0 Management tool. For more information about certificate
requirements for federation servers, see http://technet.microsoft.com/enus/library/dd807040(v=ws.10).aspx.
Before you can add any new certificates, you may have to disable the automatic certificate
rollover feature by using Windows PowerShell commands. For steps on how to add a tokensigning certificate, see http://technet.microsoft.com/en-us/library/dd807039(v=WS.10).aspx.
8
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
9
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
9. On the Details tab of the Certificate form, select Thumbprint and then click Copy to File,
as shown in the following screen shot.
10. Save the certificate without the spaces between pairs of characters. This thumbprint value is
used when you configure the connector parameters in the Microsoft Dynamics AX Connector
for Mobile Applications service.
11. This certificate must be installed in the Trusted Root Certification Authorities store on the
server machine that hosts the Microsoft Dynamics AX Connector for Mobile Applications
service.
NOTE: If you are not using a token-signing certificate that is issued by a trusted Certification
Authority, you can use a self-signed certificate. You must export this certificate from your
ADFS server and add it to the Trusted People certificate store on this machine. However, using
a self-signed certificate is not an optimal configuration choice.
Here are a few more points to keep in mind about these certificates:
Ensure that the Subject Name (CN) or Issued to property of the service
communications certificate (SSL certificate) matches the Federation Service name.
To view or edit the Federation Service name, right-click Service in the left navigation
pane, and then select Edit Federation Service Properties.
In our example, the service communications certificate has its Subject Name(CN)
property set to contosoadfs.com, which helps define the URL of the Federation Server
endpointfor example, https://contosoadfs.com/adfs/ls/.
You can validate that your service is set up correctly by opening the URL
https://contosoadfs.com/adfs/fs/federationserverservice.asmx in a browser.
10
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
For additional debugging and troubleshooting, go to the Events tab in the Federation
Services Properties form, and turn on logging for error and other events. This can help you
debug any issues by looking at the logged events in Windows Event Viewer.
11
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
The relying party is the Windows Azure Access Control Service associated with the Service Bus that
was set up in the Creating a new Windows Azure Service Bus namespace section.
1. In the left navigation pane, expand Trust Relationships, right-click Relying Party Trusts,
and then select Add Relying Party Trust.
This will open the Add Relying Party Trust Wizard that you need to follow to add your Windows
Azure Service Bus namespace as a relying party to the AD FS configuration database.
2. Click Start.
3. On the Select Data Source page, select one of the options to add data about your relying
party.
If you select the first option, Import data about the relying party published online or on
a local network, enter the federation metadata address in the text box in the following
format:
https://<AzureNamespace>-sb.accesscontrol.windows.net/FederationMetadata/200706/FederationMetadata.xml
12
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Figure 8: Add Relying Party Trust Wizard Select Data Source page
To use the second option, Import data about the relying party from a file, because your
AD FS server does not have Internet access, you need to do the following:
1. In a browser, open the address https://contosomobilesb.accesscontrol.windows.net/FederationMetadata/2007-06/FederationMetadata.xml, for
example, and save the FederationMetadata.xml file to a location.
2. Select the second option, Import data about the relying party from a file, click
Browse, and load the saved FederationMetadata.xml file.
3. Click Next.
13
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
4. On the Specify Display Name page, enter a display name or leave the default value, and
then click Next.
Figure 9: Add Relying Party Trust Wizard Specify Display Name page
14
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
5. On the Choose Issuance Authorization Rules page, ensure that the Permit all users to access
this relying party option is selected, and then click Next.
Figure 10: Add Relying Party Trust Wizard Choose Insurance Authorization Rules page
6. On the Ready to Add Trust page, click Next, and then finish the setup by clicking Close.
The Open the Edit Claim Rules dialog for this relying party trust when the wizard
closes option is selected by default. When the wizard closes, the Edit Claim Rules form will
open.
15
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
7. Click Add Rule. You will be guided through the Add Transform Claim Rule Wizard.
8. On the Select Rule Template page, in the Claim rule template field, select Pass Through
or Filter an Incoming Claim, as shown in the following screen shot, and then click Next.
9. On the Configure Rule page, enter a name for the claim rule.
10. In the Incoming claim type field, select Windows account name.
16
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
11. Select the Pass through all claim values option, as shown in the following screen shot, and
then click Next.
12. In the Edit Claim Rules form, you can see the newly created claim rule. Click Apply and then
OK to save your changes.
17
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
You can get back to the Edit Claim Rules form by right-clicking the relying party trust that
you just added and then selecting Edit Claim Rules.
18
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
19
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
1) Verify that the WS-Federation identity provider (e.g. Microsoft AD FS 2.0) option is
selected, and then click Next.
On the Edit WS-Federation Identity Provider page, enter a display name for the identity provider,
such as Contoso ADFS.
Under WS-Federation metadata, enter the federation metadata URL or the file that is available from
your configured AD FS server, as described in the Configuring an Active Directory Federation Service
for authentication section.
20
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
In the Used By section, under Relying party applications, ensure that the Service Bus check box
is selected.
21
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
1) Click the ServiceBus link, and then, in the Relying Party Application Settings section, verify
that the settings for the Realm and Token format fields are as shown as in the following screen
shot.
In the Authentication Settings section, select the identity provider to use with the relying party. The
identity provider was created in the previous section, Add and configure the identity provider.
22
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Select the Default Rule Group for ServiceBus check box to use the default rule group, as described
in the Configure rule groups section.
You will be able to view the predefined rules that have Access Control Service as the claim issuer
value. Click each rule to view the values. These rules have owner as the Input claim value, and
Listen, Manage, or Send as the Output claim value.
23
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Delete the rules that have Output claim values of Manage and Send.
24
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
25
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
26
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
In a later step, the Dynamics AX Connector for Mobile Applications service should
be deployed and run using this same account. For more information about how to
create and set up the .Net Business Connector (BC) proxy account, see Specify the
.NET Business Connector proxy account [AX 2012]
Also it is very important that the .Net BC proxy user account is added as an
Administrator on the machine running the AX Connector service
Also note the following guidance for the .Net BC proxy account
You can check which BC Proxy user account has been configured by going to AX>
System Administration> System Service Accounts
For Microsoft Dynamics Business Analyzer, you must install Microsoft .NET Framework 4.5.
For Microsoft Dynamics Business Analyzer and if SQL Server Analysis Services is not
installed on the same machine as your Microsoft Dynamics AX AOS, you must install the
ADOMDClient (v10) assembly on your AOS machine.
o
X86: http://go.microsoft.com/fwlink/?LinkId=130651&clcid=0x409
X64: http://go.microsoft.com/fwlink/?LinkId=130652&clcid=0x409
IA64: http://go.microsoft.com/fwlink/?LinkId=130653&clcid=0x409
Note: You can only run one instance of the Microsoft Dynamics AX Connector for Mobile
Applications on a machine.
27
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Figure 27: Microsoft Dynamics AX Connector for Mobile Applications Setup Wizard Welcome page
Select the I accept the terms in the License Agreement check box, and then click Next.
Figure 28: Microsoft Dynamics AX Connector for Mobile Applications Setup End-User License Agreement
28
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
On the Destination Folder page, accept the default folder location for the connector, or click Change
to select another location. Then click Next.
On the Service account page, in the Account name and Password fields, enter the name and
password for the BC Proxy user account that was previously created, and then click Next.
Click Install.
Click Finish.
Click Start > Administrative Tools > Service to open the Windows Services list.
29
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Click Start to start the Microsoft Dynamics AX Connector for Mobile Applications service. The service
will run under the context of the service user account.
30
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Parameter
Configuration
Enter the service namespace that you set up in the Creating a new
Windows Azure Service Bus namespace section, and then click Save.
Enter the service identity name that you set up in the Creating a new
Windows Azure Service Bus namespace section.
Enter the 256-bit symmetric key (DefaultKey) for the service identity
that was generated in the Creating a new Windows Azure Service Bus
namespace section.
Endpoint URI of
EmailApprovalsServices (if using
Email approvals)
Endpoint URI of
BusinessAnalyzerServiceGroup (if
using Microsoft Dynamics Business
Analyzer)
ADFS URL
31
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Support Email
An email address the mobile user will see to contact in case of any
issues. For example, support@contoso.com
On the Start menu, click the Microsoft Dynamics AX Connector for Mobile Applications shortcut.
The GUI for configuring the connector parameters will open.
Use the information in the following table to configure the connector parameters.
Note that the Endpoint URI parameters for the following services are optional:
Expense
Timesheet
Approvals
Email Approvals
Business Analyzer
If you choose not to configure one of the services, leave that field blank, and then click Save.
When the Microsoft Dynamics AX Connector for Mobile Applications service is started, you will
notice that the URL for that service does not appear, and the phone applications will not display
the corresponding feature.
Note: Windows 8 applications will fail to connect to Microsoft Dynamics AX if the corresponding
URI entry does not exist. For example, the Windows 8 Expenses app will fail to connect to
Microsoft Dynamics AX if the Endpoint URI of ExpenseServices parameter is blank or not
correct.
32
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
33
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
34
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Figure A2: Screen capture of the contextual information shown on the Overview tab
35
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Extended context for a timesheet (Time details, Time summary, and Project impact tabs)
Although the extended context for timesheets and expenses is built into the app and cant be provided
for other approval types, all the other contextual information, such as context on a tile, context on the
Overview tab, and attachments, can be customized to meet the requirements of your organization by
making configurations on the server. All customizations are performed in the following form, which is
36
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
accessible in the Microsoft Dynamics AX client under System Administration > Setup > Windows
Store > Windows application store setup.
Figure A5: Screen capture Approvals page and Tile information tab
_tableId,
_recId)
{
SalesQuotationTable t;
37
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
if(_tableId == tableNum(SalesQuotationTable))
{
t = SalesQuotationTable::findRec(_recId);
return t.invoiceAmount();
}
return 0;
}
Adding reports
You can build reports to customize the information that an approver will receive in the Approval app,
and then associate the reports with the workflow template. For example, a new report might show all
the details of the quotation that is being approved. When an approval work item is generated, the
report that displays the quotation information is rendered and included as an attachment in the email
message to the approver. The approver can then open and view the report. The following steps must
be completed if you want to include a custom report:
1) Author a new report: The new report must use a query-based data source whose root is the
same table as the workflow templates document. Continuing the example with
PSASalesQuotation from the previous sections, the new report must be based on a query whose
root table is SalesQuotationTable. This enables the context of the quotation that is being approved
to be passed to the report when it is executed.
Create a menu item: Create a new display menu item that references your new report. In order to
associate the report with the workflow template, you must complete these steps:
1. Verify that the configuration key matches the configuration key of the workflow template.
2. Use the same prefix for the menu item and the report. The prefix refers to the first three
letters of the element name in the AOT.
Pick the menu item: On the Report association tab of the Windows Store App configuration
screen, select the newly created menu item.
After you have completed these steps, the report will be rendered when an approver clicks view on
the approval item in the attachments section of the application.
Dynamics AX, but no presence indicators will be included. Lync integration in the Approvals app
utilizes the new UCWA protocol and therefore can be used only with on-premises deployments of Lync
2013 CU1. Additionally, the domain of your users will need to be added to the Allowed List, as
described in this document: http://ucwa.lync.com/documentation/ITAdmin-Configuration.
39
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
40
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Create a Windows
Azure Service Bus
namespace
Configure an Active
Directory Federation
service for
authentication
Update party
federation metadata
5
2a
Optional: Configure
Management
Reporter
The steps in the diagram correspond to sections of this document. The following list shows the order in
which you must complete these steps:
Step 1: Creating a new Windows Azure Service Bus namespace
Step 2: Configure an Active Directory Federation Service for authentication
Step 2a: Optional: Add a trust relationship and claim rule for Business Analyzer with
Management Reporter
42
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Add a trust relationship and claim rule for Business Analyzer with Management
Reporter
1) Open Trust Relationships > Relying Party Trusts.
2) In the Actions pane, click Add Relying Party Trust to display the Add Relying Party Trust
Wizard.
Click Start.
On the Select Data Source page, select the Enter data about the relying party manually option,
and then click Next.
On the Specify Display Name page, enter a display name, and then click Next.
On the Choose Profile page, select the AD FS profile option, and then click Next.
On the Configure Certificate page, click Next.
43
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
On the Configure URL page, select the Enable support for the WS-Federation Passive protocol
check box, enter your relying party WS-Federation Passive protocol URL, and then click Next. This
URL should use the following format:
https://[AzureNamespace].servicebus.windows.net/reportingsecure/Report.svc/authentication/v2/
wsfederation
44
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
On the Configure Identifiers page, add the Service Bus endpoint, and then click Next.
On the Ready to Add Trust page, click Next, and then finish the setup by clicking Close. The Open
the Edit Claim Rules dialog for this relying party trust when the wizard closes option is
selected by default. When the wizard closes, the Edit Claim Rules form will open.
Click Add Rule to display the Add Transform Claim Rule Wizard.
45
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
On the Select Rule Template page, in the Claim rule template field, select Send LDAP Attributes
as Claims as shown in the following screen shot, and then click Next.
On the Configure Rule page, enter a name for the claim rule.
46
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
In the LDAP Aattributes to outgoing claim types grid, enter the following field values and then
click Finish:
LDAP Attribute: User-Principal-Name
Outgoing Claim Type: UPN
In the Edit Claim Rules form, you can see the newly created claim rule. Click Apply and then OK to
save your changes.
You can get back to the Edit Claim Rules form by right-clicking the relying party trust that you just
added and then selecting Edit Claim Rules.
Configure settings and update the database schema for Management Reporter
Before you can use Business Analyzer with Management Reporter, you must configure the
MRServiceHost.settings.config file, and you must also add the required database schema to the
Management Reporter database. Two Windows PowerShell scripts are available to help you complete
these tasks. Download the Windows PowerShell script package from the following location:
http://go.microsoft.com/fwlink/?LinkId=389274
The package is a .zip file that contains two Windows PowerShell scripts:
Configure-ManagementReporterActOnBehalfOf Run this script to add the required database
schema to the Management Reporter database and to insert the record for the user who has
permission to act on behalf of another user.
47
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Note: The MRServiceHost.settings.config file might already contain additional rows in the
appSettings section.
3. Replace the sample values in the rows that you added with the values that are specific to your
Microsoft Dynamics AX environment, save your changes, and then restart the Management
Reporter Process Service and Management Reporter Application Service. Use the following
table to determine where the values are referenced in this white paper.
Variable
AdfsRealm
https://contosomobile.servicebus.windows
.net
AdfsIssuer
https://contosoadfs.com/adfs/ls
AdfsThumbprint
faf8b8778a50e1d07357
AdfsName
https://contosoadfs.com
48
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Variable
AdfsAudienceURI
https://contosomobile.servicebus.windows
.net
AdfsClaim
http://schemas.xmlsoap.org/ws/2005/05/
identity/claims/upn
ServiceBusDefaultIssuer
owner
ServiceBusDefaultKey
S83sFqJNg/1kgiSpqzZC+NHSJLRK0IEPuz7
kR2gbnps=
ServiceBusAddress
https://contosomobile.servicebus.windows
.net/reportingsecure/Report.svc
EnableMROverAzure
true
Note: The AdfsAudienceURI and AdfsRealm variables will likely be the same value.
Install required Management Reporter hotfixes
Before you can use Management Reporter in Business Analyzer, you must install the following
Management Reporter hotfix:
http://go.microsoft.com/fwlink/?LinkId=386401
49
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS
Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your
people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar
Microsoft software, automating and streamlining financial, customer relationship and supply chain processes in a
way that helps you drive business success.
U.S. and Canada Toll Free 1-888-477-7989
Worldwide +1-701-281-6500
www.microsoft.com/dynamics
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the
date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a
commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of
publication.
This white paper is for informational purposes only. Microsoft makes no warranties, express or implied, in this document.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of
this document may be reproduced, stored in, or introduced into a retrieval system, or transmitted in any form or by any means
(electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of
Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject
matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this
document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
2014 Microsoft Corporation. All rights reserved.
The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted
herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person,
place, or event is intended or should be inferred.
Microsoft, Active Directory, PowerShell, Microsoft .NET Framework, Microsoft Dynamics, Microsoft Lync, Windows, and Windows
Azure are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
50
CONFIGURE THE MICROSOFT DYNAMICS AX ENVIRONMENT FOR COMPANION APPS