hybrid cloud foundation - …€¦ · web viewhybrid cloud foundation. functional specification....

Functional Specification

Prepared for

Update [Customer] in Doc Properties[Enter Document Creation/Update Date Here]Version 0.1

Prepared by

[Type Author Here]Update [Author Position] in Doc PropertiesUpdate [Author Email] in Doc Properties

ContributorsUpdate [Contributors] in Doc Properties

Hybrid Cloud Foundation

Update [Customer] in Doc Properties

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.© 2017 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.

iiHybrid Cloud Foundation, Functional Specification

Revision and Signoff Sheet

Change RecordDate Author Version Change Reference

<Author> .1 Initial draft for review/discussion

ReviewersDate Name Version

ApprovedPosition

Hybrid Cloud Foundation, Functional Specification

Table of Contents

1 Introduction...............................................................................................61.1 Audience........................................................................................................71.2 Purpose of the document...............................................................................71.3 Scope of the document..................................................................................71.4 References.....................................................................................................8

2 Objectives, Constraints and Assumptions..................................................82.1 Design Objectives..........................................................................................82.2 Design Constraints.........................................................................................82.3 Design Assumptions.......................................................................................9

3 Update [Customer] in Doc Properties – Current Environment(s).............104 Design Decisions......................................................................................115 Functional Specification...........................................................................12

5.1 Heading 2 (Numbered) – Ctrl+Shift+2.........................................................125.1.1 Heading 3 (Numbered) – Ctrl+Shift+3........................................................12

6 Heading 1 (Numbered) – Ctrl+Shift+1.....................................................136.1 Heading 2 (Numbered) – Ctrl+Shift+2.........................................................13

6.1.1 Heading 3 (Numbered) – Ctrl+Shift+3........................................................136.2 Heading 2 (Numbered) – Ctrl+Shift+2.........................................................13

6.2.1 Heading 3 (Numbered) – Ctrl+Shift+3........................................................136.3 Heading 2 (Numbered) – Ctrl+Shift+2.........................................................14

6.3.2 Heading 3 (Numbered) – Ctrl+Shift+3........................................................14

7 Document Tips.........................................................................................168 Appendix A - Template Change Log.........................................................17


1 IntroductionThe intent of this document is to provide a location to document customer decisions as part of the design document. It is intended to be used in conjunction with the Azure Reference Architecture (AZRA) document and is recommended that these decisions be combined with relevant AZRA content to form a final customer deliverable.This functional specification describes Update [Customer] in Doc Properties’s cloud datacenter environment, based on Microsoft Azure Infrastructure-as-a-Service (IaaS). The primary purpose of this functional specification is to provide a definition of the solution for extending Update [Customer] in Doc Properties’s existing datacenter into Azure to provide an elastic, scalable, resilient, and extensible platform upon which business enabling services can be built and hosted. The main goal of Update [Customer] in Doc Properties is to utilize Azure to [Insert core customer objectives]. The extension of existing datacenter services into Azure will enable Update [Customer] in Doc Properties to deliver and support key business initiatives, such as [Insert key customer initiatives].

This functional specification will describe the components of Azure required to create, deploy and support new development, test, and production services and capabilities on Microsofts’ Azure Cloud platform using IaaS and PaaS services. This includes the re-hosting or migration of existing workloads onto Microsoft Azure. This functional specification includes key decisions made during the Solution Alignment Workshops delivered during the Hybrid Cloud Foundation engagement with Microsoft Consulting Services, and has leveraged Microsoft’s Azure Reference Architecture to evaluate the most appropriate solution decisions have been made, decisions in the following areas:

Cloud Computing Models and the Azure Datacenter Model Microsoft Azure Enterprise Operations Azure Subscriptions Azure Accounts and Access Permissions Microsoft Azure Management Models Azure Resource Manager Templates Microsoft Azure Compute both IaaS and PaaS Microsoft Azure Storage, Networking, Identity, Security and Operations

While giving direction to Update [Customer] in Doc Properties on how to extend its own datacenter capabilities into Microsoft Azure this functional specification captures any Update [Customer] in Doc Properties requirements expressed during the Solution Alignment Workshops.


The functional specification, design decisions and any requirements Content and decisions referred to in this document are based on the solution alignment workshops conducted by Microsoft Consulting Services (MCS) on dd/mmm-dd/mmm.

1.1 AudienceThis document has been prepared for a technical audience, and specifically the Update [Customer] in Doc Properties core Azure project team and the “extended project team” consisting in various specialists who are involved in supporting other key related areas such as monitoring, patch management, backup, identity, security, networking, and database and application hosting services within Update [Customer] in Doc Properties.

1.2 Purpose of the documentThis functional specification created by Microsoft Consulting Services frame and provide a reference of the key design decisions for extending Update [Customer] in Doc Properties’s exists datacenter capabilities into Microsoft Azure. This document should also capture any requirements Update [Customer] in Doc Properties have articulated during the Solution Alignment Workshops to enable the successful implementation of Microsoft Azure to be integrated with Update [Customer] in Doc Properties existing datacenter capabilities. This document also endeavors to identify any additional infrastructure requirements and the implications for each, including connectivity, authentication and management to enable the:

Creation of new production workloads in Microsoft Azure; Migration or moving existing workloads hosted on-premises onto Microsoft

Azure;

1.3 Scope of the documentThe scope of this document is limited to describing the possible Microsoft Azure IaaS and PaaS capabilities that are in scope for this project together with the integration capabilities each offers. It does attempt to cover every service and capability within Microsoft Azure due to the rate at which new functionality is being encompassed into the platform, however there is nothing to stop these other or new features being introduced into the solution at a later point, if required.This document also only describes the basic services in Microsoft Azure, sufficient to provide the reader with an understanding of the services, but does not define the design and integration of these services or the configuration settings in detail. The expectation is that if these are required then further design documentation will be


produced, however the production of such detailed design documentation is typically out of scope in the delivery of the standard Hybrid Cloud Foundation.

1.4 References<Document any references used in the definition of this functional specification>

Document Description

DOC-001 <Insert References where applicable>

DOC-002 <Insert References where applicable>Table 1: References

2 Objectives, Constraints and Assumptions

2.1 Design Objectives<Document the customer design objectives for the overall solution>

Number Objective

DO-001 <Insert Design Objectives>


DO-003 <Insert Design Objectives>.


DO-005 <Insert Design Objectives>Table 2: Design Objectives

2.2 Design Constraints<Document the customer design constraints for the overall solution>

Number Objective

DC-001 <Insert Design Constraints>




Number Objective


DC-005 <Insert Design Constraints>Table 3: Design Constraints

2.3 Design Assumptions<Document the customer design assumptions for the overall solution>

Number Objective

DA-001 <Insert Design Assumptions>




DA-005 <Insert Design Assumptions>Table 4: Design Assumptions


3 Update [Customer] in Doc Properties – Current Environment(s)

<Insert a high-level description of the customers’ current environment(s) and a diagram>

Figure 1: Update [Customer] in Doc Properties Overview


4 Design DecisionsDuring the Solution Alignment Workshops the following design decisions were documented.

Number Objective

DD-xxx <Insert Design Decisions>




DD-xxx <Insert Design Decisions>Table 5: Design Decisions


5 Functional Specification

5.1 Heading 2 (Numbered) – Ctrl+Shift+2 5.1.1 Heading 3 (Numbered) – Ctrl+Shift+3


6 Heading 1 (Numbered) – Ctrl+Shift+1

6.1 Heading 2 (Numbered) – Ctrl+Shift+2 6.1.1 Heading 3 (Numbered) – Ctrl+Shift+36.1.1.1 Heading 4 (Numbered) – Ctrl+Shift+4

6.2 Heading 2 (Numbered) – Ctrl+Shift+26.2.1 Heading 3 (Numbered) – Ctrl+Shift+36.2.1.1 Heading 4 (Numbered) – Ctrl+Shift+4Heading 5 – Ctrl+Shift+5Normal - Ctrl+Shift+NClearAllFormatting - Ctrl+Shift+G

Title Note - Ctrl+Shift+SNote text - Ctrl+Shift+X

Bullet List: Bullet 1 - Ctrl+Shift+A

o Bullet 2 - Ctrl+Shift+E (to increase indent, Ctrl+Shift+W to decrease indent)

Bullet 3 - Ctrl+Shift+E (to increase indent, Ctrl+Shift+W to decrease indent)

Numbered List:1. Num Bullet 1 - Ctrl+Shift+Q

a. Num Bullet 2 - Ctrl+Shift+E (to increase indent, Ctrl+Shift+W to decrease indent)

i. Num Bullet 3 - Ctrl+Shift+E (to increase indent, Ctrl+Shift+W to decrease indent)

Command Line:


Ctrl+Shift+C

Code Block:Ctrl+Shift+B

Check List: Ctrl+Shift+D Ctrl+Shift+D

6.3 Heading 2 (Numbered) – Ctrl+Shift+2Table (header repeats across page breaks):

# Table Header – Ctrl+Shift+T

Table Header – Ctrl+Shift+T

6.3.1 Num Heading 3 Style - Ctrl+Shift+Y

Table Text – Ctrl+Shift+T Table List Bullet - Ctrl+Shift+F Table List Bullet - Ctrl+Shift+F


Table Text – Ctrl+Shift+T Table List Bullet - Ctrl+Shift+F


Table Text – Ctrl+Shift+T

6.3.2 Heading 3 (Numbered) – Ctrl+Shift+3Table (header repeats across page breaks):



6.3.2.1 Num Heading 4 Style – Ctrl+Shift+H

Table Text – Ctrl+Shift+T Table List Bullet - Ctrl+Shift+F Table List Bullet - Ctrl+Shift+F


Table Text – Ctrl+Shift+T Table List Bullet - Ctrl+Shift+F





Table Text – Ctrl+Shift+T


7 Document Tips

To remove all the Visible Guidance (Hot Pink text with Grey Background) all at once:

1. Click Ctrl H to open the Find and Replace box2. Make sure your cursor is in the ‘Find what’ box.3. Click on the More button at the bottom left4. Click on the Format Button at the bottom left and select Style5. Scroll down, locate select the “Visible Guidance”6. Make sure the ‘Replace with’ box is empty:7. Click ‘Replace All”8. If not empty - click on the format button in the lower left hand corner. Scroll down

and chose ‘(no style)’then replace all.

IMPORTANT – Finalize This Document REMOVE all pink text, guidance, comments, changes, and hidden text in this document before submitting it to the customer. You can do this in two ways:

Save as PDF and send the PDF version to the customer. ~ OR ~

Inspect document and remove comments, revisions, any document properties you do not want included, personal information, and hidden text. For guidance on how to do this, see Remove hidden data and personal information from Office documents.


8 Appendix A - Template Change Log2. Added page break before to “Heading 1 (Numbered)”.3. Changed “Heading 4 Num” Style Name to “Heading 4 (Numbered)” for

consistence with other heading Style Names.4. Removed TOC inadvertently sitting behind the Blue banner on Page 1 that

was causing formatting issues when updating using command to “Update All Fields”

5. Changed Heading 5 font from “Calibri Light (Headings)” to “Segoe UI” to be inline with the rest of the document.

6. Refined List and Numbered Bullet alignment.7. Updated TOC with to include H1-H3 as seemed to be originally intended.8. Changed Style List to list Styles alphabetically.9. Added “SDM Headings” list style.10.Modified Custom Word Properties to list properties in alphabetical order.11.Added “Template Version” Custom Property to track versions of the template.12.Added shortcut keys as illustrated in the doc & shown below for

IncreaseIndent, IncreaseIndent and ClearAllFormatting shortcuts. (To modify: Customize Ribbon -> Customize Keyboard shortcuts).

13.Added Num Heading 3 & 4 for numbering in tables linked to headings.14.Set default table style to repeat header row across page breaks.


hybrid cloud foundation - …€¦ · web viewhybrid cloud foundation. functional specification....

Documents