Microsoft Dynamics GP 2013Considerations for Deploying on Windows AzureJune 2013
Deployment Considerations
Deployment Models
What Microsoft Dynamics GP deployment options are available?
Windows Azure Components
What Windows Azure services will be used when deploying Microsoft Dynamics GP?
Account Setup
What is a Window Azure Account and how is it set up?
Account SetupAccountIdentified by a Microsoft Account (formerly Windows Live ID)Billing account for Windows Azure service usage chargesCreate using Pay-as-you-Go, 6 month or 12 month pricingContains one or more subscriptionsControls usage and access to subscriptions
SubscriptionContainer for reporting usage and controlling access to Windows Azure Infrastructure Services (WAIS).Account owner sets administrative access per subscription. WAIS components are created in subscriptions.
Account
Subscription 1
Virtual Network
Virtual Machine
Subscription 2
Virtual Network
Virtual Machine
Virtual Machine
Subscription 3
Virtual Network
Virtual Machine
Virtual Machine
Getting StartedCreate AccountSelect the type of account to use (select 1-month Free Trial for limited testing on single machine only) Sign in with the Microsoft Account that will be the ownerReview the account information and select the appropriate Country/RegionProvide a mobile number to validate the accountProvide the credit card and billing information
Create SubscriptionSign into the Windows Azure Management PortalOpen the Account CenterClick to add subscriptionSelect the appropriate subscription offer
Windows Azure ComponentsVirtual Machine (VM)Windows Servers that perform roles, such as SQL Server and Web Server, for the Microsoft Dynamics GP 2013 deployment.
Virtual Network (VN)Provides a network for communication between Windows Azure Virtual Machines and potentially computers on other networks.
Storage Account (SA)Stores the data disks and VHD files for the Windows Azure Virtual Machines.
Affinity Group (AG)Keeps the virtual machines and storage accounts together for optimal performance.
Azure
Storage Account.vhd file
Data diskData disk
Virtual Machine
Virtual Machine
Virtual network
.vhd file
Affinity Group
Virtual Network Options
Extend Corporate NetworkCreate secure site-to-site connectivity between an on-premises network and a Windows Azure Virtual Network. Use to support single sign on (SSO) for corporate domain users.
Dedicate Private Virtual NetworkCreated a Virtual Network that is fully contained within Windows Azure. It is not connected to an on-premise network. Use in Service Provider scenarios with multiple customers on a single Virtual Network.
Deployment ModelsDedicated Each customer has their own Windows Azure environment and components.
HybridCustomers share some of the Windows Azure infrastructure components in this model but have dedicated virtual machines with the Dynamics GP components.
SharedCustomers share most all of the Windows Azure components in this model.
Deployment Model VisualPartner Account
Shared Subscription
Customer A Virtual
Network
Virtual Machine
Customer BVirtual
Network
Virtual Machine
Virtual Machine
Customer C Subscription
Virtual Network
Virtual Machine
Virtual Machine
Partner Account
Shared Subscription
Shared Virtual Network
Shared Virtual Machine
Customer A Virtual
Machine
Customer B Virtual
Machine
Customer B Virtual
Machine
Customer C Virtual
Network
Virtual Machine
Virtual Machine
Partner Account
Shared Subscription
Shared Virtual Network
Shared Virtual Machine
Shared Virtual
Machine
Shared Virtual Machine
Shared Virtual Machine
Dedicated Hybrid Shared
Shared Component
Dedicated Hybrid Shared
Visual
ProsFull customer isolation
Delegate admin functions to customerJoin Virtual Network to customer’s
network
Shared resources = less expensive per customer
Allows for GP components requiring dedicated OS
Shared resources = less expensive per customer
Cons No shared resources = more expensive Limited admin delegation capabilityStand alone Virtual Network (no SSO)
Not all GP components availableLimited admin delegation capability
Stand alone Virtual Network (no SSO)
Recommended when
Single customer deploymentGP components require dedicated OS
Require Virtual Network joined to customer’s network
Require separate usage billing per customer (use different subscription per
customer)
Service Provider (hosting) deploymentSome GP components require dedicated OS Service Provider (hosting) deployment
All GP components support shared OS
Us er Us er Us er
OSGP
Us erSQL
VN
OSGP
Us er
SQL
VN
OSGP
Us er
SQL
VN
OSGP
SQL
Virtual Network (VN)
OSGP (MI)
SQL SQL
Us er Us er Us er
OSGP (MT)
SQL
Virtual Network (VN)
GP (MI)
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. 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 provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.