At its core, Office 365 is the same suite of Office products and services you recognize, now provided through the cloud. Through Office 365, Microsoft offers more features in and greater access to the tools you use, both at work and at home. Office 365 is different in that it. Apr 16, 2020 Office 365 All-in-One For Dummies. By Peter Weverka and Timothy L. Warner Jun 25, 2019. 4.4 out of 5 stars 1,590. Paperback $17.99 $ 17. 99 $39.99 $39.99. One place for everything in your life. Easily store and share photos, videos, documents, and more - anywhere, on any device, free.

1. Office 365 Login Portal
2. Office 365 Onedrive Download
3. Microsoft Office 365 Login
4. Bcps One Office 365

When Using Office 365 (Home or Business), did you know you can set up multiple Microsoft accounts to be available to you when working on and saving documents?

What do I mean by this? Well, for those of us using either Office 365 consumer or O365 Business, we know that we should get our apps set up by signing into our Microsoft account when first getting set up.

For example, open up Word and click ‘File’ to get to the backstage view, then scroll down to ‘Account’ and click on it. If you’ve never signed up, you will most likely get a prompt to do so. If you’re at work, you’ll enter in your business O365 credentials. If you’re using O365 Home, you can enter in one of your Microsoft accounts.

You see in the illustration that I’m signed into a Microsoft account. But look below that and you can see I’ve connected my O365 Business account as well. So I’m using multiple accounts – efficient!

Video of How To Add Your Microsoft Accounts

I did a short video to show you how to sign in and personalize your Microsoft Office desktop apps experience.

I also did a SlideShare you can look at or download that highlights the top things to do once you buy Office 365.

Office 365 Business Accounts

Now if you’re at work, you probably won’t want to connect any personal accounts, just your business O365 account.

After you’ve signed in with your business credentials, you’ll want to connect, or add-in both your SharePoint sites and your ODB (OneDrive for Business). You do this in the backstage view – look for connected services at the bottom (see illustration above).

Office 365 Personal Accounts

If you have Office 365 Home (the $99/year subscription service), you’ll be able to add multiple Microsoft accounts to your desktop apps (Word, Excel, PowerPoint).

For my situation, I work from home, so I don’t mind having both my business O365 and personal O365 accounts all together on one computer. On this work station, I have 3 accounts and I can switch among them if I wish.

However, I really don’t need to because I’m able to save my documents into either my ODB, SharePoint or OneDrive consumer since I’ve connected all these services on my computer.

When I do a ‘Save As’ command, you’ll see I’m presented with three OneDrive or SharePoint choices. I can also choose to save to the local drive (Computer) if I wish.

This gives users a way and choice to put documents in the storage of their choosing.

Choose What’s Best for You

I hope this was helpful and perhaps gives you some ideas to make your own work flow more convenient and productive.

Note

At this time, we have a Public Preview of the native Cross-tenant mailbox migration located at https://aka.ms/CrossTenantMailboxMigration

This article explains how to migrate mailboxes and service settings from one Microsoft 365 or Office 365 organization to another Microsoft 365 or Office 365 organization in a business-merger scenario. If you have more than 500 users to migrate or a large amount of SharePoint data to migrate, it's a good idea to work with a Microsoft solution provider.

The scenario in this article is based on two fictional companies - Contoso.com and Fabrikam.com - using two separate Office 365 organizations. Contoso has purchased Fabrikam and is moving the Fabrikam users and data to the contoso.com Office 365 organization.

Scenario: Migrate using a third-party migration tool

This scenario assumes that user, group and other objects from the Fabrikam Company will be manually created in Office 365, imported into the portal via script, or merged into the Contoso Active Directory through Active Directory Domain Services (AD DS) consolidation.

When complete, all Fabrikam accounts will exist in the Contoso.com Office 365 organization, and will all use @fabrikam.com for the UPN. The final addressing scheme was chosen for simplicity and brevity but can of course be modified to meet your requirements.

Planning: Two weeks before you migrate

If using a third-party migration tool to migrate your users, purchase the needed licenses for your migration.

Client considerations

For Outlook 2010 or above, you only need to remove the Outlook user profile and create it again.

For Outlook 2007 and Outlook 2010, when you are restarting the client, auto-discover will configure the client and rebuild the .OST file.

For the Skype for Business client, once migration is complete, since the process creates a new profile, you will need to add contacts.

Tenant preparation and licensing

The source tenant is the Fabrikam Office 365 organization from which you are migrating users and data. The target tenant is the Contoso Office 365 organization to which you are migrating.

1. Increase licenses in Target Office 365 organization to accommodate all mailboxes that will be migrated from the source tenant.

2. Create Administrator accounts in source and target tenants for use in migrating from Office 365 to another Office 365. Some migration tools may require more than one admin account in the source tenant to optimize the data throughput.

Room, resource, distribution group, and user object creation in the target tenant

To create the resources in the target (Contoso) tenant:

1. If the Azure AD Connect tool will be used to sync all objects from the Contoso Active Directory Domain Services (AD DS), the objects from the source (Fabrikam) tenant AD DS must be created in the target tenant (Contoso) AD DS through consolidation.

   1. AD DS consolidation can be done using various AD DS tools. Consolidation can take extra time and planning depending on how many objects are being moved, so it can be completed ahead of the migration project.

   2. Verify that all new users and groups are synced to the Contoso.com target tenant via directory synchronization. The objects should appear as user@contoso.onmicrosoft.com in the new tenant since the Fabrikam domain has not been moved over at this time. The primary email address for the users and groups can be updated to @fabrikam.com after the domain move is complete.

2. If directory synchronization will not be used, or if any Rooms, Resources, Groups or Users are managed in the Microsoft 365 admin center of the source tenant; these objects must be created in the target tenant. Objects can be created manually in the Microsoft 365 admin center or for larger numbers import a CSV file by using the bulk add feature in the Microsoft 365 admin center, or by using Windows PowerShell.

End-user communications

To communicate the migration to the end users in your organization:

1. Create a communication plan and begin to notify users of the upcoming migration and service changes.

2. After migration, the Auto-Complete List (also known as the nickname cache) will have to be cleared on all Outlook clients. To remove all recipients from your Auto-Complete list in Outlook 2010 later, see Manage suggested recipients in the To, Cc, and Bcc boxes with Auto-Complete.

3. Make users aware of how to connect to Outlook on the web (formerly known as Outlook Web App) with their new sign on information in case they have a problem after migration.

Preparation and pre-migration activities: Three days before you migrate

Domain preparation

To prepare the domain for migration, complete the following steps.

1. Begin domain verification process on target (Contoso) tenant for the Fabrikam.com email domain.

2. In the contoso.com Microsoft 365 admin center, add the Fabrikam.com domain and create TXT records in Domain Name Systems (DNS) for verification.

   Note

   The verification will fail because the domain is still in use in the other tenant.

   Performing this step now will allow the DNS record time to propagate as it can take up to 72 hours. Final validation will occur later in the process.

Migration scheduling

To schedule the migration:

1. Create master list of user mailboxes you want to migrate.

2. Create mailbox mapping .CSV file for the third-party migration tool you are using. This mapping file will be used by the migration tool to match the source mailbox with the target tenant mailbox when migration occurs. We recommend that you use the *.onmicrosoft.com 'initial' domain for mapping the source accounts since the custom email domain will be constantly changing.

Mail exchanger record (MX record) time to live (TTL) test

Next, you'll schedule the TTL test.

1. In DNS, change the TTL value on the MX record for the primary email domain you wish to transfer to a small number (i.e. 5 minutes). If the TTL cannot be lowered to 5 minutes, make note of the lowest value. Example, if the lowest value is 4 hours, the MX record will have to be changed 4 hours before your migration begins.

2. Mx Lookup can be used to verify MX and DNS changes.

Disable directory sync in source tenant

In the source tenant Microsoft 365 admin center, disable directory sync. This process can take 24 hours or more so it must be done ahead of the migration. Once disabled in the portal, any changes to the source tenant AD DS will no longer sync to the Office 365 organization. Adjust your existing user and group provisioning process accordingly.

Migration: The day you migrate

These are the steps you'll need the day you perform the migration.

MX record change - Stop inbound mail flow

Change your primary MX record from Office 365 to domain that is not reachable, i.e. 'unreachable.example.com'. Internet mail servers attempting to deliver new mail will queue the mail and attempt redelivery for 24 hours. Using this method, some email may return a non-delivery report (NDR) depending on the server attempting to deliver the email. If this is a problem use an MX record backup service. There are many third-party services that will queue your email for days or weeks. Once your migration is complete, these services will deliver the queued mail to your new Office 365 organization.

Tip

If your TTL is short, for example, five minutes, this step can be done at the end of the work day to cause less disruption. If you have a larger TTL, you must change the MX record ahead of time to allow the TTL to expire. Example, a four hour TTL must be changed before 2 PM if you plan to begin migrations at 6 PM.

Verify your MX and DNS changes if necessary. Nslookup or a service like MxToolbox can be used to verify MX and DNS changes.

Source tenant preparation

The primary email domain, fabrikam.com, must be removed from all objects in the source tenant before the domain can be moved to the target tenant.

Office 365 Login Portal

1. If you had also set up your domain with a SharePoint Online public website, then before you can remove the domain, you first have to set the website's URL back to the initial domain.

2. Remove all Lync licenses from the users in the source tenant using Lync admin portal. This will remove the Lync Sip address connected to Fabrikam.com.

3. Reset default email addresses on Office 365 source mailboxes to the initial domain (fabrikam.onmicrosoft.com).

4. Reset default email addresses on all Distribution Lists, Rooms and Resources to the initial domain (fabrikam.onmicrosoft.com) in source tenant.

5. Remove all secondary email (proxy addresses) from user objects that are still using @fabrikam.com.

6. Set default domain in source tenant to fabrikam.onmicrosoft.com routing domain (in the admin portal, click your company name in the upper right corner).

7. Use Windows PowerShell command Get-MsolUser -DomainName Fabrikam.com to retrieve a list of all objects that are still using the domain and blocking removal.

8. For common domain removal issues, see You get an error message when you try to remove a domain from Office 365.

Target tenant preparation

Complete the verification of the Fabrikam.com domain in the contoso.com tenant. You may have to wait one hour after removing the domain from the old tenant.

1. Configure auto-discover CNAME (internal/External) optional.

2. If you are using AD FS, configure the new domain in target tenant for AD FS.

3. Begin mailbox activation in the contoso.com tenant > Assign licenses to all of the new user accounts.

4. Set the Fabrikam.com email domain as the primary address on the new users. This can be done by selecting/editing multiple unlicensed users in the portal or by using Windows PowerShell.

5. If you are not using the password hash sync feature, pass-through authentication or AD FS, set password on all mailboxes in the target (Contoso) tenant. If you are not using a common password, notify users of the new password.

6. Once mailboxes are licensed and active, transition the mail routing. Point the Fabrikam MX record to Office 365 target (Contoso) tenant. When the MX TTL expires, mail will begin to flow into the new empty mailboxes. If you are using an MX backup service, you can release the email to the new mailboxes.

7. Perform verification testing of mail flow to/from new mailboxes in the target tenant.

8. If you are using Exchange Online Protection (EOP): In the target tenant recreate mail flow rules (also known as transport rules), connectors, block lists, allow lists, etc. from source tenant.

Begin migration

To minimize downtime and user inconvenience, determine the best method for migration.

• Migration for 500 users or less: Migrate Mail Calendar and contact data to target tenant mailboxes. Limit mail migration by date if possible; for example, the last 6 months of data.

• Migration for more than 500 users: Use a multi-pass approach where you migrate contacts, calendars and only 1 week of email for all users, then on succeeding days or weeks, do multiple passes to fill in the mailboxes with older email data.

Office 365 Onedrive Download

Start your mail migration via the third-party migration tool.

1. Monitor migration progress with the tools provided by the vendor. Send out periodic progress reports during migration to management and migration team.

2. Do second or third pass migrations, optional after all migrations are complete.

At the end of migration, Outlook 2007 and 2010 will sync the entire mailbox for each user, consuming considerable bandwidth depending on how much data you migrated into each mailbox. Outlook 2013 will only cache 12 months of data by default. This setting can be configured to more or less data, for example, only 3 months of data, which can lighten bandwidth usage.

Post migration: Cleanup

User may receive NDRs when replying to migrated email messages. The Outlook Auto-Complete List (also known as the nickname cache) needs to be cleared. To remove all recipients from your Auto-Complete list in Outlook 2010 later, see Manage suggested recipients in the To, Cc, and Bcc boxes with Auto-Complete. Alternatively, add the old legacy DN as an x.500 proxy address to all users.

Sample Windows PowerShell scripts

Use the following sample Windows PowerShell scripts as a starting point for creating your own scripts.

Office 365 bulk password reset

1. Create a CSV file named password.csv.

2. Insert 'upn' and 'newpassword' columns in this file (Example: johnsmith@contoso.com,Password1)

3. Use the Windows PowerShell command:

Copy all Office 365 accounts with a specific proxy address into a CSV file

Bulk Create room mailboxes in Microsoft 365

Note

Microsoft Office 365 Login

• Before you run the following script, you need to install the Exchange Online PowerShell V2 module. For instructions, see Install and maintain the EXO V2 module. The EXO V2 module uses modern authentication.

• Typically, you can use the script as-is if your organization is Microsoft 365 or Microsoft 365 GCC. If your organization is Office 365 Germany, Microsoft 365 GCC High, or Microsoft 365 DoD, you need to edit the Connect-ExchangeOnline line in the script. Specifically, you need to use the ExchangeEnvironmentName parameter and the appropriate value for your organization type. For more information, see the examples in Connect to Exchange Online PowerShell.

Bcps One Office 365

Bulk remove secondary email address from mailboxes

Note

• Before you run the following script, you need to install the Exchange Online PowerShell V2 module. For instructions, see Install and maintain the EXO V2 module. The EXO V2 module uses modern authentication.

• Typically, you can use the script as-is if your organization is Microsoft 365 or Microsoft 365 GCC. If your organization is Office 365 Germany, Microsoft 365 GCC High, or Microsoft 365 DoD, you need to edit the Connect-ExchangeOnline line in the script. Specifically, you need to use the ExchangeEnvironmentName parameter and the appropriate value for your organization type. For more information, see the examples in Connect to Exchange Online PowerShell.