Export (0) Print
Expand All
3 out of 4 rated this helpful - Rate this topic

Office 365 deployment guide glossary

 

Applies to: Office 365 Enterprise

Topic Last Modified: 2014-02-24

Summary: Lists commonly used terms in the Office 365 environment and in these articles.

Active Directory Federation Services (AD FS): AD FS provides the various end-points that the Microsoft Federation Gateway uses to redirect clients to the AD FS server for different types of authentication. AD FS must be installed on a separate physical server that is a part of your on-premises network organization.

Active Directory Federation Services configuration database: A database used to store all configuration data that represents a single AD FS 2.0 instance or Federation Service. This configuration data can be stored using the Windows Internal Database (WID) feature included with Windows Server 2008 and Windows Server 2008 R2 or using a SQL Server database.

Autodiscover: The Exchange Autodiscover service automatically finds the correct Exchange Server host and configures Outlook 2010 or Outlook 2007 for your users. It also includes an offline address book and the Free-Busy availability service that provides availability information for your users.

Comma separated value (CSV) file: A text file in which each value is separated by a comma. It is typically used as an input file for a software program or script.

CNAME record: A canonical name record (CNAME) is a type of resource record in the Domain Name System (DNS) that is an alias for the Address (A) record that maps an IP address to the target server. The target server does not have to exist in the same domain as the CNAME record itself. You can define an alias in one domain to point to a target server in a completely different domain. Many organizations use CNAME records with web servers. An organization might point the alias www to a Web server that is hosted by a dedicated Web hosting company. For example, requests for www.contoso.com can be redirected to webserver1.fabrikam.com.

Cross-premises coexistence: Simple coexistence is an email coexistence configuration that offers only the basic feature of a unified global address list (GAL) and mail routing between the on-premises and Exchange Online organizations.

Deployment Consultant: The Deployment Consultant (Microsoft or partner) is the primary resource for customers to work with on technical and project related items. The Deployment Consultant is the primary contact for your Technical Lead.

Directory synchronization  The Windows Azure Active Directory Sync Tool replicates an organization’s on-premises Active Directory information for mail-enabled objects to the Office 365 environment. Using the Windows Azure Active Directory Sync Tool, your company’s administrators can keep your on-premises Active Directory continuously synchronized with Office 365. This not only allows you to create synchronized versions of each user account and group, but also allows GAL synchronization from your local Exchange Server environment to Exchange Online. Organizations that are deploying hybrid scenarios must deploy the Windows Azure Active Directory Sync Tool on a separate, on-premises server. The synchronization from your on-premises Active Directory to the Office 365 Active Directory environment is one way.

Domain registrar: A domain name registrar is an organization or commercial entity, accredited by the Internet Corporation for Assigned Names and Numbers (ICANN) or by a country code top-level domain (ccTLD) authority, to manage the reservation of Internet domain names in accordance with the guidelines of the designated domain name registries and offer such services to the public.

Email coexistence: Email coexistence enables organizations with on-premises Exchange Server email environments to establish a connection between their on-premises mail environment and the Office 365 Exchange Online mail environment. With coexistence configured, some users connect to Exchange Online while others continue to use the local Exchange Server environment, and all of the users can share the same email domain name. Email coexistence can be configured as either cross-premises coexistence or as a hybrid deployment.

Exchange Management Shell: The command-line interface for Exchange Server 2010 and Exchange Server 2007.

Exchange Control Panel: This Web-based console is used to manage the Exchange Online environment. The Exchange Control Panel can be accessed through the Admin area of the Microsoft cloud services Portal.

Exchange Hosted Archive: Part of the Exchange Hosted Services network, Exchange Hosted Archive provides a repository that stores email. Using EHA, organizations can manage increasingly complex retention, compliance, and regulatory requirements. The EHA systems receive a message and after being filtered the clean message is delivered to the corporate mail server. A copy is made and stored in a security-enhanced online message repository.

Note: EHA was an option in the Business Productivity Online Standard Suite service and is no longer available with Office 365. Exchange Online Archive can be used instead.

Exchange Online: A hosted email and messaging service built on Exchange Server and offered by Office 365. For organizations using on-premises Exchange Server and Exchange Online, Exchange Online is sometimes referred to as their “cloud-based Exchange organization.”

External relay: A configuration option in Microsoft cloud services Portal when mailboxes for a domain are hosted outside of Exchange Online and the mail exchange record (MX record) points to an email server outside of Exchange Online. Selecting this option requires disabling of inbound messaging.

Federation Service: A logical instance of AD FS 2.0. A Federation Service can be deployed as a stand-alone federation server or as a load-balanced federation server farm. You can configure the name of the Federation Service using the AD FS 2.0 Management snap-in. The DNS name of the Federation Service must be used in the Subject name of the SSL certificate.

Federation server: A computer running Windows Server 2008 or Windows Server 2008 R2 that has been configured to act in the federation server role. A federation server serves as part of a Federation Service that can issue, manage, and validate requests for security tokens and identity management. Security tokens consist of a collection of claims, such as a user's name or role. Federation server farm: Two or more federation servers in the same network that are configured to act as one Federation Service instance.

Federation server proxy: A computer running Windows Server 2008 or Windows Server 2008 R2 that has been configured to act as an intermediary proxy service between a client on the internet and a Federation Service that is located behind a firewall on a corporate network. In order to allow remote access to the services in Office 365, such as with a smart phone, home computer, or Internet kiosk, you need to deploy a federation server proxy.

Forefront Online Protection for Exchange (FOPE) Administration Center: The service management site for Forefront Online Protection for Exchange.

Hybrid Deployment: A hybrid deployment is an email coexistence configuration offers Exchange organizations the ability to extend the feature-rich messaging experience and administrative control they have with their existing on-premises Exchange Server organization to Office 365 and Exchange Online. A hybrid deployment provides the seamless look and feel of a single Exchange organization between an on-premises organization and an Office 365 organization. In addition, a hybrid deployment can serve as an intermediate step to moving completely to Exchange Online. A hybrid deployment offers a unified GAL and mail routing between the on-premises and Office 365 organizations plus additional messaging features typically available in an on-premises Exchange deployment, including sharing free/busy and calendar information between the organizations and the ability to move mailboxes from the on-premises organization to the Office 365 organization.

Hybrid Servers: Hybrid servers are Exchange Server 2010 Service Pack 2 (SP2) servers that are installed in your existing Exchange organization. They are required for hybrid deployments. Hybrid servers enable messaging features and messaging delivery between your existing Exchange organization and the Office 365-based Exchange organization.

single sign-on: single sign-on provides a true single sign-on (SSO) experience for users to access both the on-premises and Office 365 service offerings with a single user name and password. Additionally, single sign-on allows administrators to easily control account policies for Office 365 mailboxes by using on-premises Active Directory management tools.

Internet Message Access Protocol (IMAP): This is an application-layer Internet standard protocol used by on-premises email clients to retrieve email from a remote server over a TCP/IP connection. Microsoft Online supports email data migration from IMAP4 environments.

Journaling: A feature of Office 365 that enables Exchange to record all email communications in an organization. Journaling can be configured with Exchange Online transport rules.

Lync Online: The Office 365 solution for instant messaging, audio and video calling, and online meetings. The Lync Online service is built on Lync 2010 Server.

Mailbox size reduction: The tasks associated with reducing the overall mailbox size for all users to allow for an increase in the total number of mailboxes that can be migrated in a single migration event.

Microsoft cloud services ID: When you first sign up for Office 365, you create a new email address and password, known as a User ID, as part of the sign-up process. You use this email address and password every time you sign in to use Office 365 service offerings. With your Microsoft cloud services ID, you sign in to perform administrative tasks, view billing and account information, and use any of the services, including Exchange Online, SharePoint Online, and Lync Online.

Microsoft Federation Gateway: The Microsoft Federation Gateway is a free cloud-based service offered by Microsoft that acts as the trust broker to establish federation between your on-premises Exchange 2010 organization and Exchange Online.

FOPE: FOPE consists of layered technologies to actively help protect your organization’s inbound and outbound email from spam, viruses, phishing scams, and email policy violations.

Windows Azure Active Directory Module for Windows PowerShell: This tool installs a set of cmdlets to Windows PowerShell that you use to set up single sign-on for Office 365.

Microsoft cloud services Portal: Web portal that the designated service administrator for a customer subscribing to Office 365 services uses to manage settings for the organization. You can also manage your active subscriptions: for example, you can increase the number of user licenses, change billing details, or select a Microsoft authorized partner to help with your subscription.

Microsoft cloud services Sign-In Assistant (MOS SIA IDCRL7): The Microsoft Online Services Sign-In Assistant (MOS SIA) provides end user with sign-in capabilities to Microsoft cloud services like Office 365. The MOS SIA installs client components that allow desktop applications like Microsoft Outlook and Lync to authenticate to Microsoft cloud services. The MOS SIA also provides an improved sign-in experience so users can access Microsoft cloud services without re-entering their user names or passwords.

MX record: An MX record is a type of resource record in DNS that specifies a mail server responsible for accepting email messages on behalf of a recipient's domain and a preference value used to prioritize mail delivery if multiple mail servers are available.

Network load balancing (NLB): A dedicated application (such as Network Load Balancing) or hardware device (such as a multilayer switch, more commonly referred to as hardware load balancer (HLB)) that is used to provide fault tolerance, high availability, and load balancing across multiple nodes. For AD FS, the cluster DNS name that you create using this NLB must match the Federation Service name that you specified when you deployed your first federation server in your farm.

Office 365 desktop setup package: This application is installed on workstations that use rich clients (such as Office 2010) and connect to Office 365 service offerings. It automatically configures rich clients for use with Office 365 and manages and installs client updates.

Office Online: Online companions to Word, Excel, PowerPoint, and OneNote, which let you review and make light edits to documents directly from a browser.

Office Professional Plus: Office applications that connect to Office 365 service offerings and provide access to documents, email, and calendars from a variety of clients. Office Professional Plus includes Office Online, the online companions to Word, Excel, PowerPoint, and OneNote, which let you review and make light edits to documents directly from a browser.

Outlook Web App: This is the browser based email client used to access Exchange Online. Formerly known as Outlook Web Access.

Relying party: A Federation Service or application that consumes claims in a particular transaction.

Relying party trust: In the AD FS 2.0 Management snap-in, a relying party trust is a trust object that is created to maintain the relationship with another Federation Service, application, or service (in this case Office 365) that consumes claims from your organization’s Federation Service.

Remote PowerShell: A Windows PowerShell feature that allows scripting of routine tasks and access to raw data for reports.

RSS feed: A frequently updated communication channel for announcements from Microsoft cloud services. Announcements come in the form of service alerts, planned and unplanned outages, and maintenance.

Security Token Service (STS): The web service that authenticates clients by validating credentials that are presented by a client. The STS can issue to a client a security token for a successfully authenticated client.

Service continuity: The process and procedures required to maintain or recover critical services during a business interruption.

Service interruption: Any event, whether anticipated (for example, a public service strike) or unanticipated (for example, a power outage), which disrupts the normal course of business operations at the organization’s location. Similar terms: outage, service interruption.

Service request: A service request (SR) is how customers engage Office 365 support for reactive and proactive issues.

Service Support Admin: Customer role that has read only permissions to all company objects. Also has the ability to manage individual services.

SharePoint Online: The Office 365 solution for collaboration. The SharePoint Online service is built on SharePoint Server 2010.

Single-label domain (SLD): SLDs are DNS names that do not contain a suffix, such as .com, .corp, .net, or .org. SLDs are not supported in Office 365 and Exchange Online deployments. For example, “contoso” is an SLD, and therefore is not supported. However, “contoso.com” is not an SLD, and therefore is supported.

Single sign-on: See Identify Federation.

SMTP relay: Allows organizations to use Exchange Online as an SMTP service for mail originating outside of the Exchange Online environment, for example SMTP-enabled applications such as fax servers.

SPF record: The Sender Policy Framework (SPF) record specifies which computers are authorized to transmit email from a domain. This helps to prevent others from using your domain to send SPAM or other malicious email. If your ISP has implemented SPF, you must create an SPF record to allow Microsoft Exchange Online to send email from your domain.

User Principal Name (UPN): A user account name (sometimes referred to as the user logon name) and a domain name identifying the domain in which the user account is located. This is the standard usage for logging on to a Windows domain. The format is josh@contoso.com (similar to an email address).

User Principal Name (UPN) suffix: The part of the User Principal Name to the right of the @ character. The default UPN suffix for a user account is the Domain Name System (DNS) domain name of the domain that contains the user account. Alternative UPN suffixes may be added to simplify administration and user logon processes by providing a single UPN suffix for all users. The UPN suffix is used only within the Active Directory forest, and it does not have to be a valid DNS domain name.

Velocity migrations: Bulk migrations of user mailboxes from an on-premises messaging system to the Exchange Online system. Each bulk migration occurs within a scheduled migration window.

 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.