• Microsoft Dynamics NAV Team Blog

    Microsoft Dynamics NAV 2013 R2 available in the Windows Azure Portal under MSDN subscription

    • 8 Comments

    Ever wondered what it is like to work with Microsoft Dynamics NAV on Windows Azure - but found it too cumbersome even with our nice Windows Azure provisioning tools?  Then this might be something for you. 

    Today we have made Microsoft Dynamics NAV 2013 R2 easily available on Windows Azure with just a few clicks. The Microsoft Dynamics NAV 2013 R2 image is an exclusive offer for MSDN subscribers and includes a fully functional, ready to use Microsoft Dynamics NAV 2013 R2 installation including Microsoft SQL Server. The MSDN subscription gives you the well-known discounted prices and allows you to use it for development, test, and demo purposes, but not for production purposes.

    How to get it? Make sure you have an MSDN subscription and the subscription has Windows Azure benefits activated. Then follow these steps:

     

    1. Sign in to the Windows Azure Portal using your MSDN subscription.
    2. Choose the + sign at the bottom of the Portal page.
    3. Choose Compute, point to Virtual Machine, and then choose From Gallery.
    4. Select the MSDN filtering checkbox as shown in the following screenshot. This will filter the list to only show the available MSDN images.

    1. Choose the Microsoft Dynamics NAV 2013 R2 image.
    2. Choose the arrow in the lower-right corner.
    3. Fill in the relevant fields about the virtual machine as described in the following list:
      1. Specify the name of the virtual machine.
      2. Specify the size of the virtual machine, such as Medium.
      3. Specify the user name and password for connecting to the virtual machine.
      4. Specify the region  where you want to host your virtual machine, such as West Europe.
      5. Verify the remaining parameters. In most cases, the default values are sufficient.
    4. Choose the Finish icon to start the provisioning process.
    5. Once the image is provisioned after a few minutes, you can use Remote Desktop to connect to it. In the Azure Portal Virtual Machine page, choose the newly created image, and then choose Connect. Use the credentials that you specified step 7.

    When you are connected to the VM, you are welcomed to the Microsoft Dynamics NAV 2013 R2 virtual machine on Windows Azure:

    No further configuration is required and you can immediately start using the clients and the development environment.

    Best regards

    Kamil Koclega & Morten Jensen from the Dynamics NAV team

  • Microsoft Dynamics NAV Team Blog

    Update Rollup 4 for Microsoft Dynamics NAV 2013 R2 has been released

    • 9 Comments

    Update rollup 4 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

    • AU – Australia
    • DE - Germany
    • DK - Denmark
    • FR - France
    • IT - Italy
    • NA – North America
    • NL – Netherlands
    • NZ – New Zealand
    • SE - Sweden
    • UK - United Kingdom

     

    New in update rollup 4 

    Beginning with update rollup 4, the update rollups for Microsoft Dynamics NAV 2013 R2 now also includes hotfixes for the upgrade toolkit. 

     

    Where to find update rollup 4

    You can download update rollup 4 from KB 2930617 - Update Rollup 4 for Microsoft Dynamics NAV 2013 R2 (Build 36078).

    The hotfixes that have been released since update rollup 3 are listed in KB 2930617. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages: 

    CustomerSource:

    PartnerSource

     

    More Information

    For more information about update rollups for Microsoft Dynamics NAV 2013 R2, see Announcement of update rollups for Microsoft Dynamics NAV 2013 R2.

  • Microsoft Dynamics NAV Team Blog

    Update Rollup 11 for Microsoft Dynamics NAV 2013 has been released

    • 8 Comments

    Update rollup 11 for Microsoft Dynamics NAV 2013 (Build 36076) has been released.

    Update rollup 11 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

    • AU - Australia
    • DE - Germany
    • DK - Denmark
    • FR - France
    • IT   - Italy
    • NA - North America
    • NL - Netherlands
    • NZ - New Zealand
    • SE - Sweden
    • UK - United Kingdom

    Where to find update rollup 11

    You can download update rollup 11 from KB 2930616 - Update Rollup 11 for Microsoft Dynamics NAV 2013 (Build 36076).

    The hotfixes that have been released since update rollup 10 are listed in KB 2930616. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages:

    CustomerSource:

    PartnerSource:

    More Information

    For more information about update rollups for Microsoft Dynamics NAV 2013, see Announcement of new hotfix process for Microsoft Dynamics NAV 2013.

  • Microsoft Dynamics NAV Team Blog

    Microsoft Dynamics NAV 2009 R2, Microsoft Dynamics NAV 2013, and Microsoft Dynamics NAV 2013 R2 Compatibility with Microsoft Windows Server 2012 R2

    • 5 Comments

    At the time when we released Microsoft Dynamics NAV 2009 R2, Microsoft Dynamics NAV 2013, and Microsoft Dynamics NAV 2013 R2, all supported client and server operating systems were tested. However since that time, Windows Server 2012 R2 has become available. 

    Over the last few months, the Microsoft Dynamics NAV team has been testing the compatibility, and we are now proud to announce that Microsoft Dynamics NAV 2009 R2, Microsoft Dynamics NAV 2013, and Microsoft Dynamics NAV 2013 R2 are compatible with Windows Server 2012 R2!

    For more information, see the System Requirements on PartnerSource.

  • Microsoft Dynamics NAV Team Blog

    Update Rollup 3 for Microsoft Dynamics NAV 2013 R2 has been released

    • 2 Comments

    Update rollup 3 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

    • AU – Australia
    • DE - Germany
    • DK - Denmark
    • FR - France
    • IT - Italy
    • NA – North America
    • NL – Netherlands
    • NZ – New Zealand
    • SE - Sweden
    • UK - United Kingdom

     

    Where to find update rollup 3

    You can download update rollup 3 from KB 2918538 - Update Rollup 3 for Microsoft Dynamics NAV 2013 R2 (Build 36035).

    The hotfixes that have been released since update rollup 2 are listed in KB 2918538. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages: 

    CustomerSource:

    PartnerSource

     

    More Information

    For more information about update rollups for Microsoft Dynamics NAV 2013 R2, see Announcement of update rollups for Microsoft Dynamics NAV 2013 R2.

  • Microsoft Dynamics NAV Team Blog

    Update Rollup 10 for Microsoft Dynamics NAV 2013 has been released

    • 0 Comments

    Update rollup 10 for Microsoft Dynamics NAV 2013 (Build 36005) has been released.

    Update rollup 10 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

    • AU - Australia
    • DE - Germany
    • DK - Denmark
    • FR - France
    • IT   - Italy
    • NA - North America
    • NL - Netherlands
    • NZ - New Zealand
    • SE - Sweden
    • UK - United Kingdom

    Where to find update rollup 10

    You can download update rollup 10 from KB 2918536 - Update Rollup 10 for Microsoft Dynamics NAV 2013 (Build 36005).

    The hotfixes that have been released since update rollup 9 are listed in KB 2918536. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages:

    CustomerSource:

    PartnerSource:

    More Information

    For more information about update rollups for Microsoft Dynamics NAV 2013, see Announcement of new hotfix process for Microsoft Dynamics NAV 2013.

  • Microsoft Dynamics NAV Team Blog

    Understanding and Configuring Session Timeouts

    • 0 Comments

    When you start the Microsoft Dynamics NAV Windows client or the Microsoft Dynamics NAV Web client, a connection is established with the Microsoft Dynamics NAV Server instance, and a corresponding session is added on Microsoft Dynamics NAV Server. Microsoft Dynamics NAV Server includes several timeout settings that determine when a session closes because of inactivity, a lost connection, or the client closes.

    The Developer and IT Pro Help for Microsoft Dynamics NAV 2013 R2 includes a new topic that explains the session timeout behavior and configuration. For more information, see Understanding and Configuring Session Timeout in the MSDN Library.

  • Microsoft Dynamics NAV Team Blog

    Uploading large files from the Web client

    • 0 Comments

    If like me you’ve been tinkering with your Lumia 1020 smartphone and snapping some high-resolution photos over the holidays, you may be wondering whether Microsoft Dynamics NAV 2013 R2 can handle such large photo sizes on the Microsoft Dynamics NAV Web client.

    Let's say you want to capture photos of your product catalogue (using the Photo action on the Item card). When uploading large files such as high-resolution photos, Microsoft Dynamics NAV will show the following error:

    The file that you are trying to use is too large. Clearly. Whilst Microsoft Dynamics NAV defaults to 4MB uploads on the Web client, you will be pleased to hear it takes just a minor tweak to your IIS configuration to support larger file uploads: 

    1. Launch the IIS Configuration Manager (in this example I am using IIS 8 but similar steps apply to earlier versions).
    2. Select the Microsoft Dynamics NAV web site in the left pane and then double-click Request Filtering.
    3. Right-click and select Edit Feature Settings… in the context menu.
    4. Set field Maximum allowed content length to an appropriate value such as 100000000 (in bytes) and click OK.
    5. Now select the Microsoft Dynamics NAV web site in the left pane again and double-click the Configuration Editor.
    6. Make sure that the From field is set to "Microsoft Dynamics NAV 2013 R2 Web Client Web.config"
    7. Set field Section to system.web/httpRuntime
    8. A number of properties should appear. Set maxRequestLength to an appropriate value such as 100000 (this time it is in kilobytes) and click the Apply action on the right.

     

    The new settings should take effect immediately without the need for an IIS or site reset.

    Go ahead and try to upload a large file now and BANG! the upload succeeds.

    You can read more about the maxRequestLength property here:

    http://msdn.microsoft.com/en-us/library/system.web.configuration.httpruntimesection.maxrequestlength(v=vs.110).aspx

    Best regards,

    Lukasz Zoglowek and Mike Borg Cardona

  • Microsoft Dynamics NAV Team Blog

    Update Rollups and Project Considerations for Upgrade, Maintenance and New Implementations

    • 28 Comments

    More and more partners are beginning to work with the update rollups. They find a lot of value in applying the latest application and platform fixes up front, instead of waiting for a customer to report those. Update rollups also simplify the way fixes are discovered and surfaced.

    So with this blog post, we want to provide a more detailed picture of the update rollups, their purpose, and their usage scenarios so that you are aware of the rollup release process and components, and so that more of you start using them. We would also like to provide our look at how to adopt and use the update rollups within various stages of the implementation project lifecycle.

    What is an update rollup?

    Update rollups are released monthly for Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2: 

    Released update rollups for Microsoft Dynamics NAV 2013 R2

    Released update rollups for Microsoft Dynamics NAV 2013

    An update rollup is a set of files that includes all hotfixes (application and platform) and regulatory features that have been released for the versions of Microsoft Dynamics NAV that are listed above. 

    They are cumulative, meaning that they include hotfixes and regulatory features that were released in the earlier update rollups for the specific product version.

    Each rollup contains the following:

    • Accumulated application change log (TXT format) compared to the originally release of the specific product version (the RTM release).
    • Application change log (TXT format) compared to the previous rollup - the “delta”.
    • Only the application objects that changed since the RTM version are included in the FOB and TXT files provided with the rollup.
    • Each application object is marked with rollup version number (version number + build number) to make it possible to see which objects have been changed in which rollup.
    • The latest version of all (not only the changed ones) platform components (executables and .dll assemblies). These components are also stamped with a version number and a build number.

    Application changes:

    Platform components:

    Hotfixes that are included in the update rollups do not always include translation. In that case, the translation for such changes are provided with the next RTM version of  Microsoft Dynamics NAV (major releases or minor release). Regulatory features included in the rollup are almost always translated; however, in rare cases the translation is provided with the following monthly update rollup.   

    Update rollups are currently released for 10 countries: Australia, Germany, Denmark, France, Italy, North America (Canada, US, Mexico), Netherlands, New Zealand, Sweden, United Kingdom.

    Local hotfixes for the following countries are currently not included in update rollups: Austria, Belgium, Switzerland, Spain, Finland, India, Iceland, Norway.

    Scenarios

    Maintenance. Applying rollups for the countries/regions where they are available.

    If you have a version of the running application for which you would like to apply the update rollup, you can follow this high level flow:

    • Find the latest rollup available for your application version here:
    • See the KB article for the UR to find the full list of application and platform changes as well as regulatory updates included in it. The list is divided by country/region. For instance, here are the KB articles for the latest available rollups:
    • Based on the urgency and relevance of the application and platform changes, current project stage, customer situation and other surrounding factors decide whether you want to apply the UR now, or wait for the next one. We strongly recommend that you always apply the latest UR to gradually reduce the amount of regressions, merging, issues and to be compliant with the latest regulatory requirements. 
    • If you are on the RTM version merge your application objects with all objects included with the latest rollup.
    • If you are on the URn version – filter out the objects which were changed since URn till the latest available UR and merge your application objects with those objects. You can use the Version List field to see in which rollup (build) they were changed. 

    Maintenance. Applying hotfixes for the countries where update rollups are not available.

    For these cases the process of applying the hotfixes and regulatory updates is the same as it was before the UR concept was introduced, namely the changes relevant to all countries/regions (W1 changes) should be applied one by one.

    However, URs can aid this process as well as you can obtain all W1 changes by downloading the latest W1 UR and merge them into your country version. You can find W1 URs by clicking at “Show additional information” and looking at their Fix Name which you can see when you download the UR:

    Platform components are country independent, therefore the platform updates can also be obtained from W1 UR and deployed for any country/region-specific version of Microsoft Dynamics NAV.

    Major releases, minor releases, and update rollups

    URs are different from the major and minor releases. Every major and minor release contains new application and platform features and functionality as well as hotfixes, while the URs only contain hotfixes and regulatory updates. So when a major release or minor release has been released, we create a new branch for the next release and continue to maintain both branches.

    Let’s dissect the process based on the Microsoft Dynamics NAV 2013 version as an example (see the illustration below).

    When Microsoft Dynamics NAV 2013 version was released, we created a new branch for Microsoft Dynamics NAV 2013 R2 development. As we’ve been building Microsoft Dynamics NAV 2013 R2 functionality, we kept fixing Microsoft Dynamics NAV 2013 and kept releasing URs for it.

    Relevant fixes from the Microsoft Dynamics NAV 2013 version were merged into the Microsoft Dynamics NAV 2013 R2 version in the course of its development. In many cases they had to be redesigned to fit the new code and new functionality of Microsoft Dynamics NAV 2013 R2.

    Therefore, when Microsoft Dynamics NAV 2013 R2 was released, not all fixes included in the latest available Microsoft Dynamics NAV 2013 UR were included in it. The process of finding and merging relevant fixes into the latest branch is a continuous process, and there will be a certain lead time until the fixes from the releases are synchronized between branches. So, for instance, the majority of the fixes which were available in Microsoft Dynamics NAV 2013 UR7 were included into Microsoft Dynamics NAV 2013 R2 UR1, and the process of merging of relevant fixes will go on.

    When considering upgrade or a new implementation of the new major release or minor release, we recommend that you always upgrade to (or start from) the latest available UR for it. If there is a particular hotfix which is available in the previous version of Microsoft Dynamics NAV, but it not yet available in the latest release, you can always request it to be merged there using the normal support process “How to create a new support case”.  It is also always possible to only update the platform components with the updated ones coming from a corresponding UR (technical upgrade), although the best practice would be to keep the application objects updated to the latest UR as well.

    Microsoft Dynamics NAV 2013 R2 hotfixes are also periodically merged into Microsoft Dynamics NAV 2013 and will be eventually available in the upcoming URs. Similarly, if there is a particular hotfix which is available in the current version of Microsoft Dynamics NAV, but it not yet available in the previous release, you can also request it to be merged there using the same support process “How to create a new support case”. 

    We will continue to release URs for the Microsoft Dynamics NAV 2013 release and future releases periodically, synchronizing relevant fixes between them over time.

    Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2 are maintained following the old process - you can request hotfixes on case by case basis, no update rollups available for those product versions. 

    The following timeline illustrates the process.

     

    Conclusion

    It is highly recommended to implement the update rollups. We look forward to hearing your feedback and suggestions to how this process could be made more convenient for you to assess and absorb the changes.

     

    Kind regards,

    Microsoft Dynamics NAV Team

     

    Updated on January 16, 2014: We removed two sentences that were misleading around the upgrade rollups and the Upgrade Toolkit. We apologize for the confusion.

  • Microsoft Dynamics NAV Team Blog

    Delivering more choice with Zetadocs Express

    • 0 Comments

    Equisys has released a new version of Zetadocs Express for Microsoft Dynamics NAV that not only supports Microsoft Dynamics NAV 2013 R2, but also includes the ability for customers to archive documents to network folders on their file servers.

    Connects people to documents

    For those that don’t know, Zetadocs Express provides the ability to send Microsoft Dynamics NAV reports by email.  It also enables you to use ‘drag and drop’ to store any document, such as an invoice from a supplier, alongside its corresponding Microsoft Dynamics NAV record. These documents can be retrieved via the Document FactBox in Microsoft Dynamics NAV, or from the document archive by business users without Microsoft Dynamics NAV.

    The new release allows customers to store these documents in SharePoint Online, SharePoint Server or network folders on your file server. Customers not ready to deploy SharePoint can use network folders initially and then switch to SharePoint later for advanced search features and filtered views.

    Windows 8.1, Windows Server 2012 R2 and Microsoft Dynamics NAV 2013 R2

    There’s also more platform choice with support for Windows 8.1, Windows Server 2012 R2, and Microsoft Dynamics NAV 2013 R2 Windows client. A future update will add support for the Microsoft Dynamics NAV 2013 R2 Web client. You can see a brief preview video of this on YouTube

    Download Zetadocs Express

    Zetadocs Express is the foundation member of the Zetadocs for NAV document management family. It is available at no additional cost to Microsoft Dynamics NAV 2013 & Microsoft Dynamics NAV 2009 customers on a Business Ready Enhancement Plan.

    The new version of Zetadocs Express can be downloaded from CustomerSource, PartnerSource and the Zetadocs website.

  • Microsoft Dynamics NAV Team Blog

    Convergence 2014 Customer Excellence Awards Nominations – Last Call!

    • 0 Comments

    Evangelize successful Microsoft Dynamics NAV customers at Convergence 2014! Check out the details and submission process for Customer Excellence Awards here:

    http://www.microsoft.com/dynamics/convergence/atlanta14/Customer-Excellence.aspx.

    Customer Excellence Awards recognize, honor, and celebrate customer organizations that are achieving outstanding success with their Microsoft solutions. In each award category, finalists and, subsequently, award winners, will be chosen on their ability to provide amazing experiences for their customers through the use of their Microsoft Dynamics solution. Nominations will be closing January 13.

  • Microsoft Dynamics NAV Team Blog

    Now Available: New How Do I Videos for Microsoft Dynamics NAV 2013 R2 on MSDN

    • 2 Comments

    Check out the latest videos on the Microsoft Dynamics NAV Developer Center. We've added to the How Do I Series to support the latest release: http://msdn.microsoft.com/en-us/dynamics/nav/dn524022

    These videos target the developer audience for Microsoft Dynamics NAV. Here is a sampling of the more than 20 titles that have been released to help you get started with Microsoft Dynamics NAV 2013 R2:

    • How Do I: Do Full SQL Tracing for Microsoft Dynamics NAV 2013 R2
    • How Do I: Use the Debugger in Microsoft Dynamics NAV 2013 R2
    • How Do I: Get Started with Windows PowerShell for Microsoft Dynamics NAV 2013 R2
    • How Do I: Migrate from Multiple Companies to a Multi-tenant Architecture in Microsoft Dynamics NAV 2013 R2

    More videos are in the works and will target both the platform and the application, so check back often to see what’s been added. All videos are in English.

     

  • Microsoft Dynamics NAV Team Blog

    Update Rollup 2 for Microsoft Dynamics NAV 2013 R2 has been released

    • 3 Comments

    Update rollup 2 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

    • AU – Australia
    • DE - Germany
    • DK - Denmark
    • FR - France
    • IT - Italy
    • NA – North America
    • NL – Netherlands
    • NZ – New Zealand
    • SE - Sweden
    • UK - United Kingdom

    Also, update rollup 2 includes Cumulative Update 1 for Microsoft Dynamics NAV 2013 R2.

    Where to find update rollup 2

    You can download update rollup 2 from KB 2913982 - Update Rollup 2 for Microsoft Dynamics NAV 2013 R2 (Build 35800).

    The hotfixes that have been released since update rollup 1 are listed in KB 2913982. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages:

    CustomerSource:

    PartnerSource

     

    More Information

    For more information about update rollups for Microsoft Dynamics NAV 2013 R2, see Announcement of update rollups for Microsoft Dynamics NAV 2013 R2.

  • Microsoft Dynamics NAV Team Blog

    Microsoft Visual Studio 2013 Now Supported for RDLC Report Design

    • 0 Comments

    We are happy to announce that we have added support for using Microsoft Visual Studio 2013 (Professional, Premium, and Ultimate editions) to create and modify RDLC reports. This lets you use the latest version of Microsoft Visual Studio when designing reports for Microsoft Dynamics NAV 2013 R2.

    To enable Microsoft Visual Studio 2013 support, you must install the hotfix from the Knowledge Base article 2907585. After the hotfix is installed, when you design reports from the Microsoft Dynamics NAV Development Environment, Microsoft Visual Studio 2013 is automatically used if it is available on the computer running the development environment; otherwise, Microsoft Visual Studio 2012 is used if it is available. There is no option to choose which version of Microsoft Visual Studio to use if both Microsoft Visual Studio 2013 and Microsoft Visual Studio 2012 are installed on the development environment computer. With regard to editing RDLC reports for Microsoft Dynamics 2013 R2, there is no functional difference between using Microsoft Visual Studio 2012 or Microsoft Visual Studio 2013, and RDLC reports that are edited with Microsoft Visual Studio 2013 can be edited later with Microsoft Visual Studio 2012 if needed.

     

    Best regards,

    the Microsoft Dynamics NAV team

  • Microsoft Dynamics NAV Team Blog

    How to: Set up your Microsoft Dynamics NAV installation for Single Sign-on with Office 365 using Windows PowerShell

    • 0 Comments

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

    // Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)

    In our blog post How to: Validate that Microsoft Dynamics NAV 2013 R2 is correctly configured to support Single Sign-on with Office 365, we presented the Microsoft Dynamics NAV Best Practices Analyzer, a tool that you can use in order to validate your single sign-on (SSO) configuration of Microsoft Dynamics NAV. Not only does it validate your Microsoft Dynamics NAV and Windows Azure Active Directory (WAAD) configuration, it has another big advantage of assisting you in setting up your environment for SSO by providing meaningful and suggestive error messages which help you build your way through this lengthy process. The entire list of steps needed for setting up SSO with Office 365 in Microsoft Dynamics NAV is completely described in this how-to video

    In the previous paragraph I have just mentioned that this is a “lengthy process” which many times can become a rather unpleasant troubleshooting experience. We have collected this feedback and addressed this problem by providing the system administrators willing to set this environment up with a powerful Windows PowerShell cmdlet.

    This cmdlet is called Set-NavSingleSignOnWithOffice365 and it can completely automate the process of configuring your Microsoft Dynamics NAV Web Client to support SSO with Office 365. For more information on the usage of this cmdlet and all the possible scenarios where its power can be leveraged, refer to the official Microsoft Dynamics NAV Help topic, which will be released with the next MSDN Library refresh: Walkthrough: Setting up your Microsoft Dynamics NAV installation for Single Sign-on with Office 365 using Windows PowerShell.

    Note: The cmdlet can fully automate the configuration process provided that the needed parameters are specified when executing it. Generating and importing the security certificates that secure the Client – Server communication channel is performed separately and is subject to another upcoming topic with the next MSDN Library refresh: How to: Create a Self-signed Security Certificate Using PowerShell Script.

    In the following section, you will find information about setting up your Microsoft Dynamics NAV installation for single sign-on with Office 365 using Windows PowerShell.

    Setting up your Microsoft Dynamics NAV Installation for Single Sign-on with Office 365 using Windows PowerShell

    Microsoft Dynamics NAV supports federated user authentication with Windows Azure Active Directory (Windows Azure AD). This is the Identity Provider service used by Office 365. As a matter of fact, every time a new Office 365 subscription is provisioned, the Windows Azure AD tenant for this subscription is also created. Thus, when Microsoft Dynamics NAV is configured for federated authentication with a WAAD tenant, a single sign-on (SSO) user experience is achieved between Microsoft Dynamics NAV and the Office 365 Web Applications and any other applications that leverage the single sign-on capability provided by the Windows Azure AD tenant. 

    The Set-NavSingleSignOnWithOffice365 cmdlet can help you perform this configuration task by automating all the steps of this process. To sum up, this cmdlet performs the following operations: 

    1. It first validates that both your Microsoft Dynamics NAV Server and Microsoft Dynamics NAV Web Server are ready for this change. 
    2. It validates that your Office 365 credentials are valid.
    3. Once the validation steps are performed, the cmdlet starts the configuration:
      1. It links your Microsoft Dynamics NAV User account to your Office 365 account by providing your Office 365 email address as the AuthenticationEmail for the Microsoft Dynamics NAV User account.
      2. It configures the Microsoft Dynamics NAV Server by changing the values of the following configuration settings: ClientServicesFederationMetadataLocation, ClientServicesCredentialType and ServicesCertificateThumbprint.
      3. It configures the Microsoft Dynamics NAV Web Server by changing the values for the following configuration settings: ClientServicesCredentialType, ACSUri and DnsIdentity.
      4. It configures the WAAD tenant by creating a Service Principal that represents the Microsoft Dynamics NAV Web Client.
    4. If any of the configuration sub-steps of step 3 fail, the cmdlet reverts all the changes made to your Microsoft Dynamics NAV Server and Web Server up until that point. 

    Prerequisites

    • Office 365 subscription
      If you already have your Office 365 subscription, you can ignore this step. Otherwise, sign up for a free trial Office 365 plan. We recommend that you use a plan such as Office 365 Enterprise E1 as your test site, or that you sign up for a trial developer plan. A trial plan includes an administrative account whose credentials you will need to provide for the WAAD configuration. For example, if your Office 365 site is Solutions.onmicrosoft.com, your administrative account can be admin@solutions.onmicrosoft.com. For more information, see Select an Office 365 plan for business.
    • Azure Active Directory Tenant Management Components
      The cmdlet relies on the presence of the following components on your system:

      Microsoft Online Services Sign-In Assistant for IT Professionals

      Windows Azure Active Directory Module for Windows PowerShell

      You can download and install these components from the links provided above. If you have to choose between 32-bit and 64-bit versions of components, then download the version that matches your Windows Operating System type. To determine the operating system type, open File Explorer, and then choose This PC in the navigation pane. On the ribbon, in the System group, choose System properties. The operating system type appears next to System type in the System section.
    • Microsoft Dynamics NAV user account
      You have to  have a valid NAV user account. For more information, see How to: Create Microsoft Dynamics NAV Users in the MSDN Library.
    • Microsoft Dynamics NAV environment
      Setting up SSO requires that you have both the Microsoft Dynamics NAV Server and Web Server installed. 
    • Security Certificate Used to Secure the Server – Web Server Communication Channel
      Setting up user authentication types other than Windows for the Microsoft Dynamics NAV environment requires securing the Server – Client (or Web Server in this case) communication. This can be done using a security certificate. The Set-NavSingleSignOnWithOffice365 cmdlet assumes that you have already imported the security certificate in your certificate store. You can either use a security certificate issued by a trusted certificate authority (see Walkthrough: Implementing Security Certificates in a Test Environment) or you can use a self-signed certificate (see How to: Configure User Authentication for the Microsoft Dynamics NAV Web Client). The latter approach is not recommended in a production environment; however, it is an alternative to consider when testing your environment.

    Importing the Automated Configuration Module 

    In order to run the Set-NavSingleSignOnWithOffice365 cmdlet, you first need to open Windows PowerShell as an administrator. This can be done by right-clicking on the Windows PowerShell program and choosing “Run as administrator”.

    Then navigate to your Microsoft Dynamics NAV DVD, then to the WindowsPowerShellScripts\ NAVOffice365Administration folder. 

    Next, run the following cmdlet in order to import the NAVOffice365Administration PowerShell module:

    Import-Module .\NAVOffice365Administration.psm1 

    Automating the Single Sign-on Configuration in a One-Computer Microsoft Dynamics NAV Environment

    Once the prerequisites are fulfilled and the Office 365 Administration module is imported, the sufficient condition for setting up SSO with Office 365 is satisfied by simply running the Set-NavSingleSignOnWithOffice365 cmdlet with the following parameter set on the computer that hosts the Microsoft Dynamics NAV components:

    Set-NavSingleSignOnWithOffice365-NavServerInstance “ServerInstanceName” -NavWebServerInstanceName “WebServerInstanceName” -NavUser “YourNavUser” -AuthenticationEmail “YourOffice365Email” -NavServerCertificateThumbprint “SecurityCertificateThumbprint”

    ServerInstanceName represents the name of your Microsoft Dynamics NAV Server instance. You can find the names for the Microsoft Dynamics NAV Server instances running on your computer by running the Get-NAVServerInstance cmdlet.

    WebServerInstanceName represents the name of your Microsoft Dynamics NAV Web Server instance. You can find the names for the Microsoft Dynamics NAV Web Server instances running in your IIS by running the Get-NAVWebServerInstance cmdlet. 

    YourNavUser represents the name of your NAV User account.

    YourOffice365Email represents the email address of your Office 365 User account. It is in the form username@o365tenant.onmicrosoft.com. This user should have administrative privileges.

    SecurityCertificateThumbprint represents the thumbprint for the security certificate used for securing the Client – Server communication channel. For more information, refer to the “Prerequisites” section of this article. You can get the list of thumbprints for your certificates by issuing this Windows PowerShell command:

     Get-ChildItem -Path "Cert:\LocalMachine\My"

    Note: You can avoid providing this parameter if you already have your Microsoft Dynamics NAV Server configured with a security certificate. This applies to Microsoft Dynamics NAV installations in the Windows Azure environment, and other environments where any credential type other than Windows is active and functional.

    Once the Set-NavSingleSignOnWithOffice365 cmdlet is run, a dialog box will open, requesting your Office 365 account user name and password. 

    Automating the Single Sign-on Configuration in a Multi-Computer Microsoft Dynamics NAV Environment

    This configuration type assumes that your Microsoft Dynamics NAV Server and Web Server are on different computers. This means that you need to run the Set-NavSingleSignOnWithOffice365 cmdlet on each of these computers separately with a different parameter set in order to correctly configure your Microsoft Dynamics NAV Web Client for SSO with Office 365.

    Running the cmdlet on the Microsoft Dynamics NAV Server computer 

    To configure your Microsoft Dynamics NAV Server for SSO, you need to run the cmdlet with the following parameter set:

    Set-NavSingleSignOnWithOffice365-NavServerInstance “ServerInstanceName” -NavUser “YourNavUser” -NavServerCertificateThumbprint “SecurityCertificateThumbprint” -SkipWebServerConfiguration

    Notice the SkipWebServerConfiguration switch, which specifies that the Microsoft Dynamics NAV Web Server components should not be configured at all.  

    Running the cmdlet on the Microsoft Dynamics NAV Web Server computer

    To configure your Microsoft Dynamics NAV Web Server for SSO, you need to run the cmdlet with the following parameter set:

    Set-NavSingleSignOnWithOffice365-NavWebServerInstanceName “WebServerInstanceName” -AuthenticationEmail “YourOffice365Email” -SkipNavServerConfiguration

    Notice the SkipNavServerConfiguration switch, which specifies that the Microsoft Dynamics NAV Server should not be configured at all.  

    Additional Remarks and Considerations 

    Running the cmdlet fails because the NAV Server fails to start / restart

    You can find more information about the Microsoft Dynamics NAV Server failure reason in the event log. This error most likely occurs because of the impossibility of the Microsoft Dynamics NAV Server to properly configure the ACL for the ports used by the server’s communication endpoints. In some situations, when there are URLACL entries for the same ports but reserved by other services (including other installed Microsoft Dynamics NAV Servers), the removal procedure fails because of insufficient privileges. The user account running the Microsoft Dynamics NAV Server needs to have administrative permissions for the modification of the URLACL to succeed. That is why, in order to overcome this issue, you can try one of the following:

    1. Remove the URL ACL entries manually (see Walkthrough: Configuring Web Services to Use SSL (SOAP and OData) for more information) or
    2. Set your Microsoft Dynamics NAV Service to run as on Administrator account on your computer.

    Running the cmdlet in a multitenant Microsoft Dynamics NAV environment 

    Only one tenant can be automatically configured at a time, so the Microsoft Dynamics NAV Tenant name needs to be provided as the NavTenant parameter to the Set-NavSingleSignOnWithOffice365 cmdlet.

    Avoiding the Office 365 Credentials dialog box

    You can fully automate the script, and thus avoid the Office 365 Credentials dialog box by providing the credentials as parameters:

    You use the AuthenticationEmail parameter to specify the Office 365 account email and the AuthenticationEmailPassword parameter to specify the Office 365 account password. Be aware that the latter parameter should be a SecureString.  

    Running the cmdlet for a Microsoft Dynamics NAV Web Server that is hosted in complex network topology

    Setting the trust relationship between the Microsoft Dynamics NAV Web Client and Windows Azure AD requires specifying a remote endpoint for the Microsoft Dynamics NAV Web Client in the Windows Azure AD Service Principal that is created for this web application.

    If the Microsoft Dynamics NAV Web Server runs behind a DNS or another network component that changes / rewrites the Web Client’s address, the Set-NavSingleSignOnWithOffice365 cmdlet is not able to compute this address, since it only runs on the local computer. 

    You can overcome this situation by providing the cmdlet the address as seen remotely for your Microsoft Dynamics NAV Web Client. The parameter you need to pass this address to is NavWebAddress.

     

    Best regards

    The Microsoft Dynamics NAV Office 365 team.

Page 2 of 41 (615 items) 12345»