Microsoft Enterprise Services Work Order
Work Order Number
6EST213-332207-404756
(Microsoft Affiliate to complete)
This Work Order consists of the terms and conditions below, and the provisions of the
Microsoft Business and Services Agreement reference U5434814, effective as of
01.07.2018 (the "Agreement"), and any attachments or exhibits referenced in this Work
Order, all of which are incorporated herein by this reference. In this Work Order
“Customer,” “you,” or “your” means the undersigned customer or its affiliate and
"Microsoft", “we,” “us,” or “our” means the undersigned Microsoft affiliate.
By signing below the parties acknowledge and agree to be bound to the terms of this
Work Order, the Agreement and all other provisions incorporated in them. This Work
Order is effective as of the date that Microsoft signs this Work Order. Regardless of any
terms and conditions contained in a purchase order, if any, the terms of this Work Order
apply.
Customer Microsoft Affiliate
Name of Customer (please print) Name
MAJANDUS- JA Microsoft Estonia OU
KOMMUNIKATSIOONIMINISTEERIUM
Signature Signature
Customersignatoryname Mssignatoryname
Name of person signing (please print) Name of person signing (please print)
Customerfullname MSfullname
Title of person signing (please print) Title of person signing (please print)
Customerjobtitle MSjobtitle
Signature date Signature date(effective date)
Customersignaturedate Mssignaturedate
Name of Customer or its Affiliate that executed the Agreement (if different from
Customer above)
EnterpriseServicesWorkOrderv7.0(WW)(ENG)(Aug2020) [CP] Page 1 of 7
Does Customer issue or require a Customer purchase order for the payment of
Microsoft Services? [ ] Yes or [ X ] No
If “No” is selected above, Customer represents and warrants that it does not require
purchase order(s) be submitted to Microsoft for payment of the Microsoft Services Fees
listed herein. Customer will not withhold payment of Microsoft’s invoice due to the
absence of a purchase order reference.
If no purchase order is required, Customer must complete "Customer invoice
information" below and ensure it is accurate or revised in a timely manner. Further, the
below “Customer invoice information” must be completed prior to: (a) Customer signing
this Work Order; and (b) Microsoft invoicing Customer.
Customer invoice information
Name of Customer Contact Name (Receives invoices under this Work
Order)
MAJANDUS-JA
KOMMUNIKATSIOONIMINISTEERIUM Ando Leppiman
Street Address Contact E-Mail Address
Harju 11
[email protected]
City State/Province Phone
Tallinn 00372625 6481
Country Postal Code Fax
Estonia 15072
1. Consulting Services and Fees.
1.1. Term.
The consulting services will commence on 31.03.2021 or the date Microsoft begins
providing the services, whichever is earlier (the “Consulting Commencement Date”), and
will expire on 30.06.2021 or the date Microsoft concludes the services, whichever is later
(the “Consulting Expiration Date”).
1.2. Description of Services.
Microsoft will perform the work described in the Statement of Work Digital Advisory
Services for Hybrid Cloud Architecture, Version 1 Final, 03.04.2021. Any dates
provided for consulting services are estimates only.
EnterpriseServicesWorkOrderv7.0(WW)(ENG)(Aug2020) [CP] Page 2 of 7
1.3. Consulting Services Fees.
Microsoft will invoice Customer on a monthly basis and Customer will pay the following
rates and any reasonable out of pocket travel and living expenses (if any, which may be
defined in the table below as “Other Charges”). Any total fee stated is an estimate only.
Customer is responsible for paying all fees incurred in connection with these consulting
services under this Work Order. The fees do not include fees for Products. Unless
otherwise specified in the invoice, Customer will pay Microsoft within 30 calendar days of
the date of Microsoft invoice.
Microsoft will not invoice you for the services provided. Any tax burden resulting from
these unpaid benefits shall be incurred by you. Both parties declare that the market value
of these Services amounts to 51.300,00[USD]. Such Microsoft funding is available until
expiry date 30/06/2021 and at this date our Services will be deemed complete, this
Work Order shall be considered as expired and we shall have no further obligation to
continue to provide any services or deliverables to you. Funding that is not completely
used before the validity date will not be refunded. You have no further claims in that
case.
Digital Advisory Services Capacity
Role/Service Rate Quantity Subtotal Total USD
Digital Architect 205,20 250 hr 51.300,00 51.300,00
Subtotal 51.300,00
Microsoft Investment (IO code: 3454150) (51.300,00)
Total Estimated Fees (excluded taxes) 0,00
1.4. Changes to the Work Order Term
Work Order Termination
Termination.
Either party may terminate this Work Order if the other party is in material breach or
default of any obligation that is not cured within 30 days’ written notice of such breach
or default.
Termination for Convenience.
Customer may terminate this Work Order at any time for convenience by providing
Microsoft with 30 days prior written notice, “Notice Period”.
EnterpriseServicesWorkOrderv7.0(WW)(ENG)(Aug2020) [CP] Page 3 of 7
Effect of Termination.
In case of termination for convenience, Customer will pay Microsoft for all services
provided up to the end of the Notice Period.
Additionally, if Customer terminates for convenience and requests Microsoft to cease
delivery prior to the end of the Notice Period, then (i) Microsoft will stop delivery upon
the date requested; and (ii) Customer will pay for any undelivered but planned hours for
each Microsoft resource(s) for the period between the date requested to cease services
and the end of the Notice Period, or an amount equal to 80 hours per Microsoft resource
engaged on this Work Order, whichever is greater.
In addition to any applicable payment, as outlined above, Customer will also pay an
additional termination for convenience fee in the amount of 20% of the difference
between the Total Estimated Fees amount identified in the Consulting Services Fees
section above and the total amount invoiced at the conclusion of the Notice Period.
2. Use, ownership and rights.
2.1. Products.
“Product” means all products identified in the Product Terms, such as all Software, Online
Services and other web-based services, including pre-release or beta versions. Product
availability may vary by region. “Product Terms” means the document that provides
information about Microsoft Products available through volume licensing. The Product
Terms document is published on the Volume Licensing Site
(http://www.microsoft.com/licensing/contracts or successor site) and is updated from
time to time.
All products and related solutions provided under this Work Order will be licensed
according to the terms of the license agreement packaged with or otherwise applicable
to such product. Customer is responsible for paying any licensing fees associated with
Products.
2.2. Fixes.
“Fixes” means Product fixes, modifications, enhancements, or their derivatives, that
Microsoft either releases generally (such as service packs), or that Microsoft provides to
Customer when performing Professional Services (all support, planning, consulting and
other professional services or advice, including any resulting deliverables provided to
Customer under this Work Order, to address a specific issue. “Professional Services”
means Product support services and Microsoft consulting services provided to Customer
under this Work Order. “Professional Services” or “services” does not include Online
Services, unless specifically noted.
Fixes are licensed according to the license terms applicable to the Product to which
those Fixes relate. If the Fixes are not provided for a specific Product, any other use terms
Microsoft provides with the Fixes will apply.
EnterpriseServicesWorkOrderv7.0(WW)(ENG)(Aug2020) [CP] Page 4 of 7
2.3. Pre-existing Work.
"Pre-existing Work" means any computer code or other written materials developed or
otherwise obtained independent of this Work Order.
All rights in Pre-existing Work shall remain the sole property of the party providing the
Pre-existing Work. Each party may use, reproduce and modify the other party's Pre-
existing Work only as needed to perform obligations related to Professional Services.
2.4. Services Deliverables.
“Services Deliverables” means any computer code or materials, other than Products or
Fixes that Microsoft leaves with Customer at the conclusion of Microsoft’s performance
of Professional Services. Upon payment in full for the Professional Services, Microsoft
grants Customer a non-exclusive, non-transferable perpetual, fully paid-up license to
reproduce, use and modify the Services Deliverable, solely in the form delivered to
Customer and solely for Customer’s internal business purposes, subject to the terms and
conditions of this Work Order.
2.5. Affiliates’ rights.
"Affiliate" means any legal entity that a party owns, that owns a party, or that is under
common ownership with a party. "Ownership" means, for purposes of this definition,
control of more than a 50% interest in an entity.
Customer may sublicense the rights contained in this subsection relating to Services
Deliverables to its Affiliates, but Customer's Affiliates may not sublicense these rights and
Customer's Affiliates' use must be consistent with the license terms contained in this
Work Order.
2.6. Reservation of rights.
All rights not expressly granted are reserved to Microsoft.
3. Restrictions
Customer must not (and is not licensed to) (1) reverse engineer, decompile or
disassemble any Product, Fix, or Services Deliverable; (2) install or use non-Microsoft
software or technology in any way that would subject Microsoft's intellectual property or
technology to obligations beyond those included in any other license terms; or (3) work
around any technical limitations in a Product, Fix or Services Deliverable or restrictions in
Product documentation. Except as expressly permitted in this Work Order or Product
documentation, Customer must not (and is not licensed to) (1) separate and run parts of
a Product or Fix on more than one device, upgrade or downgrade parts of a Product or
Fix at different times, or transfer parts of a Product or Fix separately; or (2) distribute,
sublicense, rent, lease, lend, or use any Products, Fixes, or Services Deliverables, in whole
or in part, or use them to offer hosting services to a third party.
EnterpriseServicesWorkOrderv7.0(WW)(ENG)(Aug2020) [CP] Page 5 of 7
4. Microsoft Professional Services Data Protection Addendum and
Confidentiality.
“Professional Services Data” means all data, including all text, sound, video, image files,
or software, that are provided to Microsoft by, or on behalf of, Customer (or that
Customer authorizes Microsoft to obtain from an Online Service) or otherwise obtained
or processed by or on behalf of Microsoft through an engagement with Microsoft to
obtain Professional Services.
The Microsoft Professional Services Data Protection Addendum in effect on the effective
date of this Work Order and available on the Volume Licensing Site at
https://aka.ms/ProfessionalServicesDPA is incorporated herein by this reference.
Limitations or exclusions in the Agreement that apply to the limitation of liability arising
out of either party’s confidentiality obligations will apply to Professional Services Data in
the same manner that they apply to Customer Data.
5. Attachments
The following documents are attached at the execution of this Work Order:
Statement of Work: Digital Advisory Services for Hybrid Cloud
Architecture,Version 1 Final, 03.04.2021
6. Microsoft Contact
Customer contact for questions and notices about this Work Order.
Microsoft Contact Name
Phone Contact E-Mail Address
EnterpriseServicesWorkOrderv7.0(WW)(ENG)(Aug2020) [CP] Page 6 of 7
EnterpriseServicesWorkOrderv7.0(WW)(ENG)(Aug2020) [CP] Page 7 of 7
Scope
Digital Advisory Services for Hybrid Cloud Architecture
Prepared for
MKM - Estonia
3/4/2021
Version 1 Final
Prepared by
Michael Pramateftakis
Architect CEE
[email protected]
Prepared for MKM
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, our
provision of this document does not give you any license to these patents, trademarks, copyrights, or other
intellectual property.
The descriptions of other companies’ products in this document, if any, are provided only as a convenience to
you. Any such references should not be considered an endorsement or support by Microsoft. Microsoft cannot
guarantee their accuracy, and the products may change over time. Also, the descriptions are intended as brief
highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products,
please consult their respective manufacturers.
© 2014 Microsoft Corporation. All rights reserved. Any use or distribution of these materials without express
authorization of Microsoft Corp. is strictly prohibited.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
ii
Scope, Digital Advisory Services for Hybrid Cloud Architecture, Version 1, Draft
Prepared by Michael Pramateftakis
"HybridArchitectureECIFScope", Template Version 4
Prepared for MKM
Revision and Signoff Sheet
Change Record
Date Author Version Change Reference
05/02/2021 Michael Pramateftakis 1 Initial draft for review/discussion
04/03/2021 Michael Pramateftakis 1 Final verion
Reviewers
Name Version Approved Position Date
iii
Scope, Digital Advisory Services for Hybrid Cloud Architecture, Version 1, Final
Prepared by Michael Pramateftakis
"HybridArchitectureECIFScope (2).docx", Template Version 4
Prepared for MKM
1. Table of Contents
1 Introduction ............................................................................................................................................ 5
2 Project Vision and Scope ................................................................................................................... 6
2.1 Vision Statement ........................................................................................................................................... 6
2.2 Scope of Project ............................................................................................................................................ 6
2. 2.2.1 High-level hybrid cloud architecture ................................................................................ 6
3. 2.2.2 Azure role design........................................................... Error! Bookmark not defined.
4. 2.2.3 Specification of usage scenarios ........................................................................................ 7
5. 2.2.4 Mitigation strategies ............................................................................................................. 7
6. 2.2.5 PoC specification and delivery support ............................................................................ 7
7. 2.2.6 Project risk assessment update .......................................................................................... 7
8. 2.2.7 Creation of blueprints .......................................................................................................... 7
2.3 Out of scope ................................................................................................................................................... 8
2.4 Deliverables..................................................................................................................................................... 8
2.5 Indicative Timeline........................................................................................................................................ 8
iv
Scope, Digital Advisory Services for Hybrid Cloud Architecture, Version 1, Final
Prepared by Michael Pramateftakis
"HybridArchitectureECIFScope (2).docx", Template Version 4
Prepared for MKM
1 Introduction
Microsoft Digital Advisory Services were invited by MKM to assist with envisioning the future
hybrid cloud architecture of Estonia and define cloud use cases.
The engagement shall cover architecture of hybrid cloud infrastructure with appropriate usage
scenarios for each case, from legacy datacenter infrastructure to hybrid and edge cases (Azure
Stack and Azure Edge), over to public cloud.
Part of the engagement is going to cover mitigation strategies for issues around cryptographic
capabilities, security features and data sovereignty issues. An update of risk assessment reports
created previously shall also happen within the scope of this engagement.
Finally, specification of appropriate proof-of-concept scenarios as well as guidance towards
creation of blueprints for core specified functionality are also going to be part of this
engagement.
Page 5
Scope, Digital Advisory Services for Hybrid Cloud Architecture, Version 1, Final
Prepared by Michael Pramateftakis
"HybridArchitectureECIFScope (2).docx", Template Version 4
Prepared for MKM
2 Project Vision and Scope
2.1 Vision Statement
This engagement shall provide Digital Advisory Services to the government of Estonia to
support ideation and envisioning of the future cloud infrastructure of Estonia. The architecture
will be hybrid, including existing legacy infrastructure, Azure Stack, Azure Edge, as well as public
cloud infrastructure. Part of the engagement will cover the specification of use cases for each
kind of infrastructure, as well as definition of appropriate proof-of-concept implementations for
core parts of envisioned functionality.
2.2 Scope of Project
Within the engagement, Microsoft will work on the following key workstreams:
• Envision a high-level hybrid cloud approach aligned with the customer needs, addressing
hybrid scenarios by incorporating Azure Stack Hub and Edge scenarios.
• Role specifications for Azure, edge and Azure Stack
• Preliminary specification of usage scenarios
• Mitigation strategy for use cases
• Project risk assessment updates
• PoC specifications
• Creation of high-level approach to project blueprints
The scope points above are explained below in more detail.
2.2.1 Envision of High-level hybrid cloud & edge approach
In this part of the engagement, a high-level hybrid architecture principles (hybrid and edge
approach) will be designed according to Microsoft best practices. The architecture will include
existing legacy infrastructure and provide a high-level view on how the infrastructure can be
extended by using Azure Stack and Azure Edge capabilities, as well as by using public cloud
services. This part of the engagement will be based on previous customer input regarding the
current state of the legacy architecture.
2.2.2 Role specifications for Azure, edge and Azure Stack
In this part of the engagement, we will focus on specifying the role each kind of infrastructure
should play in the overall architecture. This will enable alignment of specific functionality with
Page 6
Scope, Digital Advisory Services for Hybrid Cloud Architecture, Version 1, Final
Prepared by Michael Pramateftakis
"HybridArchitectureECIFScope (2).docx", Template Version 4
Prepared for MKM
specific types of infrastructure, aligned with overall security, manageability, and scalability
requirements.
2.2.3 Preliminary specification of usage scenarios
Different classes of infrastructure are appropriate for different usage scenarios. In this part of the
engagement, a set of scenarios will be defined for each class. As an example, scenarios that
involve highly sensitive data will use either legacy infrastructure or Azure Stack, while scenarios
dealing with open data may run on public cloud or edge infrastructure depending on their
characteristics.
2.2.4 Mitigation strategy for use cases
Previous customer input revealed a set of requirements in the adoption of the cloud which
cannot be supported directly at this time. These stem mainly from compliance requirements
with local laws and are mostly related to security of the system and resilience issues. In this part
of the engagement, we will develop mitigation strategies to work around these issues.
2.2.5 Project risk assessment update
The customer has documentation that contains a set of risk assessment reports created for
implementation of modern work capabilities. In this part of the engagement, we will update the
reports to cover newly introduced architecture including Azure Stack, Azure Edge, and public
cloud services.
2.2.6 PoC specification and platform support
As the infrastructure architecture evolves, key parts of the infrastructure will be validated with
proof-of-concept implementations. This part of the engagement aims at providing support in
defining the PoCs correctly and providing technological and design support regarding the
implementation platform to the delivery teams. Delivery oversight will be provided to the
development parties as needed.
Note: Implementation of the PoCs is not part of this engagement’s scope. We consider
implementation to be a customer/partner responsibility.
2.2.7 Creation of high-level approach to project blueprints
Blueprints are Azure artifacts that can be used to deploy sets of infrastructure services with
appropriate configuration and applied policies. In this part of the engagement, we will assist
with designing blueprints for deploying and reinforcing infrastructure according to the
Page 7
Scope, Digital Advisory Services for Hybrid Cloud Architecture, Version 1, Final
Prepared by Michael Pramateftakis
"HybridArchitectureECIFScope (2).docx", Template Version 4
Prepared for MKM
envisioned architecture, as well as apply configuration according to best practices and required
security and compliance requirements.
2.3 Out of scope
Anything not explicitly included in the above section is out of scope for Microsoft during this
project. Areas out of scope for this project also include (but not limited to):
Business process Designing functional business components of the solution is not
reengineering included.
Application Development of applications is not in scope for this project.
Development
Detailed design All architecture and use cases defined in this engagement will be of a
specification high level. No detailed design for any given workload can be developed
within the scope of this engagement.
Workload analysis No specific workloads will be analyzed in the scope of this engagement.
The scope only includes recommendations of use cases for each class
of infrastructure
Workload migration No workload migration activities are not in scope for this project.
2.4 Deliverables
The following list enumerates the deliverables in scope for this engagement:
• High-level hybrid & edge approach document
• Use cases document containing a list of cases as follows:
o Use cases recommended for legacy infrastructure
o Use cases for Azure Stack
o Use cases for Azure Edge
o Use cases for public cloud
• Risk assessment document update
• Mitigation strategy document
• Blueprint approach document
Page 8
Scope, Digital Advisory Services for Hybrid Cloud Architecture, Version 1, Final
Prepared by Michael Pramateftakis
"HybridArchitectureECIFScope (2).docx", Template Version 4
Prepared for MKM
2.5 Indicative Timeline
We estimate that the total timeline to complete the activities is approximately 3 to 4
calendar months.
Page 9
Scope, Digital Advisory Services for Hybrid Cloud Architecture, Version 1, Final
Prepared by Michael Pramateftakis
"HybridArchitectureECIFScope (2).docx", Template Version 4