My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Microsoft 12/19/2017
>
Contracts
>
6 Years Then Destroy
>
2020
>
Microsoft 12/19/2017
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/4/2018 3:19:25 PM
Creation date
4/4/2018 3:03:08 PM
Metadata
Fields
Template:
Contracts
Contractor's Name
Microsoft
Approval Date
12/19/2017
Council Approval Date
12/13/2017
End Date
12/31/2020
Department
Information Technology
Department Project Manager
Kevin Walser
Subject / Project Title
Microsoft Enterprise Agreement
Tracking Number
0001127
Total Compensation
$1,264,285.68
Contract Type
Agreement
Contract Subtype
Technology
Retention Period
6 Years Then Destroy
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
22
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Aftiilate acknowledges and agrees that it is the cote Enrolled Affiliate, and sole Licensee, <br />with respect to each Tenant Enrollment, and Enrolled Affiliate will be solely responsible for <br />each Tenant Enrollment's compliance with the terms and conditions of the Lead Enrollment <br />and the associated Enterprise Agreement. <br />c. Price level under each Tenant Enrollment will he the same level that is reflected on the <br />Product Selection Form and Is based upon the aggregate of license and Software <br />Assurance quantity of the Lead Enrollment and each Tenant Enrollment as described in <br />the Product Selection Form or as described in other agreement documents. <br />d. The effective date, term, anniversary dates and payment dates for each Tenant Enrollment <br />shall coincide with the Lead Enrollment Identified above. <br />e. All Product Licenses that are not covered in the scope of the Online Services must be <br />purchased under the Lead Enrollment, including Enterprise Products and Additional <br />Products. <br />f. Enrolled Affiliate must submit an annual true up order for each Tenant Enrollment per the <br />terms of the Lead Enrollment and must comply with the requirements set forth in the Lead <br />Enrollment under the Section titled "Order Requirements", with the exception of the initial <br />order requiring a minimum of 250 Licenses for each Tenant Enrollment and ,(if applicable) <br />the submission of an Update Statement under each Tenant Enrollment. The initial order <br />and all subsequent orders will be submitted separately for each respective Tenant <br />Enrollment. For any included Affiliate that remains licensed with on -premise Licenses and <br />does not require a separate Tenant Enrollment, orders must be placed under the Lead <br />Enrollment. <br />g. If the Enrolled Affiliate is Transitioning Licenses (as contemplated in the Lead Enrollment), <br />Licenses from which the Enrolled Affiliate Is Transitioning will be reduced from the Lead <br />Enrollment Identified above and the Licenses to which the EnrolledAffiliate Is Transitioning <br />will be ordered under the specific Tenant Enrollment(s), <br />h. Due to technical considerations for multi -tenant deployment, described below, Licenses <br />may not be reassigned between the Tenant Affiliates. <br />i. Each Tenant Enrollment may be managed separately in VLSC (or a successor site) by the <br />individuals whose names and contact Information are Identified In Appendix A, or by other <br />individuals to whom each TenantAfnliate'may delegate such management responsibilities, <br />to the some extent as if such Tenant Affiliate had enrolled separately as an Enrolled Affiliate <br />under the Enterprise Agreement pursuant to its own Enrollment. <br />j. Enrollment acceptance and order reminders will be sent to contact(s) Identified on the Lead <br />Enrollment only. <br />3. Technical considerations for multi -Tenant deployment <br />Each Tenant Affiliate will be assigned a separate Tenant, provided that it complies with the temts and <br />conditions of this amendment. Each Tenant Will require Tenant Administrator(s) <br />with unique login <br />credentials, and each Tenant Affiliate will manage its Tenant separately in the administrator console. <br />This will permit and require each Tenant Affiliate to be managed end operated independently of the <br />other. Due to the independent nature of each Affiliate Tenant from the other, there will be a number of <br />technical boundaries associated with managing or using the tenants together, including but not limited <br />to those in the following list: <br />a. No ability to provide consolidated administrative reporting or control across Tenants. <br />b. No automated ability to move users between Tenants. For example, if a user moves from <br />one affiliate to another, this will require Tenant Administrators to manually create new User <br />accounts, download mall to PST files and import, and delete old user. <br />c. No consolidated Global Address List for all Tenants. <br />tl. No ability for a single individual with the same Tenant Administrator login credentials to <br />manage more than one Tenant. However It is possible for a single person to have unique <br />login credentials for each tenant as long as they track their own login credentials. <br />AmendmenNpp v4.0 M130,M9 <br />7 9 <br />Page 2 of 5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.