Creating and Deleting Sites in SharePoint Online #Office365

By , March 23, 2015 12:32 pm

You can use the SharePoint Online Management Shell to efficiently manage users, sites, and organizations instead of using the SharePoint Online Administration Center.

What is the difference between SharePoint Online cmdlets and Office 365 cmdlets?

The set of SharePoint Online Management Shell cmdlets differs from the set of Office 365 for professionals and small businesses cmdlets. SharePoint Online Management Shell cmdlets manage SharePoint Online users and sites, whereas Office 365 cmdlets manage Office 365 level tasks such as domain, license, organization information, and services. They both manage users and groups. However, Office 365 users and groups are not only for SharePoint Online services, but also for Exchange Online and Lync Online Services.

Set up the SharePoint Online Management Shell environment for SharePoint Online global administrators

Perform the following:

  1. Install Windows PowerShell 3.0 from Windows Management Framework 3.0.
  2. Install the SharePoint Online Management Shell from the Microsoft Download Center.
  3. Click Start>All Programs>SharePoint Online Management Shell.
  4. Run Connect-SPOService. For example, Connect-SPOService -Url -credential, where:
    • Url is the URL of the SharePoint Online Administration Center.
    • Credential is the user name to which you want to grant access to the SharePoint Online Administration Center site.
  5. Try it out! For example, run Get-SPOSite to get a list of all sites.


Lab Example



You will see there are two new site created




Delete A Sharepoint Online Site Sp-delete


Plan for Office 365 – the Internet BANDwidth usage part

By , March 16, 2015 12:45 pm

There are many factors involved in migrating to or co-exist (Hybrid) with O365. Every organization has or can difference experience based on their current messaging setup. Your existing Exchange environment has to be at some standard or meet some criteria before you start moving to Office Email Cloud. For example if you an undamaged (no mailbox quota, unlimited public folder etc) exchange then first you need to do some cleanup before you move to O365 (Hybrid or Cutoover). There are some basic building blocks you need to follow

Estimating Bandwidth Usage

There are many variables to consider when estimating network traffic. Some of these variables are:

  • The Office 365 service offerings that your organization has subscribed to.
  • The number of client computers in use at one time.
  • The type of task each client computer is performing.
  • The performance of your Internet browser software.
  • The capacity of the network connections and network segments associated with each client computer.
  • Your organization’s network topology and the capacity of the various pieces of network hardware.

Network Bandwidth Calculators you can use with Office 365

 There are calculators available to assist you with estimating network bandwidth requirements. These calculators work for on-premises as well as Office 365 deployments. You can use the Exchange client network bandwidth calculator to estimate the bandwidth required for a specific set of Outlook, Outlook Web App, and mobile device users in your Office 365 deployment. With the Lync Server 2010 and 2013 bandwidth calculator, you enter information about users and the Lync Online features you want to deploy, and the calculator helps you determine bandwidth requirements.

Migration Velocity Testing

Testing and validating your Internet bandwidth (download, upload, and latency constraints) are vital to understanding how to achieve high-velocity migration of on-premises mailbox content to the Office 365 and Exchange Online environments. Slow or latent connectivity reduces the number of mailbox migrations that can be completed during a migration window. Be sure to perform the following steps:

  • Test and confirm that your organization’s Internet bandwidth can manage the network impact of Office 365 migrations.
  • Assess internal network bandwidth availability for Office 365 migration events.
  • Make use of available network tools such as:
  • Determine your download, upload, and latency between your on-premises environment and the nearest Microsoft cloud services data center. The following activities can help with this task:
    • Ping to determine the IP address of the nearest Microsoft cloud services data center from your location.
    • Consult a third-party IP mapping website (for example, to determine that data center’s location.
    • Use a speed test website (for example, to determine the upload, download, and latency statistics between your on-premises environment and the nearest location to the Microsoft cloud services data center.
    • Determine the periods in which the on-premises Exchange system is heavily used (for example, during backups).


Strategies to Improve Migration Velocity

To improve migration velocity as well as reduce your organization’s bandwidth constraints, you should consider the following:

  • Reduce mailbox sizes. Smaller mailbox size improves migration velocity.
  • Public Folder Cleanup – make sure cleanup your public to meet the public folder mailbox in O365
  • Use the mailbox move capabilities with an Exchange hybrid deployment. With an Exchange hybrid deployment, offline mail (.OST files) does not require re-download when migrating to Exchange Online. This significantly reduces your download bandwidth requirements.
  • Schedule mailbox moves to occur during periods of low Internet traffic and low on-premises Exchange use. When scheduling moves, understand that migration requests are submitted to the mailbox replication proxy and may not take place immediately.

For more detailed information, see Exchange Online Migration Performance and Best Practices.

Installing Windows PowerShell for Azure Rights Management – Part 2-2

By , March 12, 2015 12:25 pm

connecting and accessing the Aadrm Service

$PSVersionTable – shows the current version of PowerShell






Now we need to enable the service
Get-Aadrm shows the curent status of the service










Installing Windows PowerShell for Azure Rights Management – Part 1-2

By , March 9, 2015 12:13 pm

This is what you need to work with Rights Management in Azure

his table lists the prerequisites to install and use Windows PowerShell for Azure Rights Management.

Requirement More information
A version of Windows that supports the Rights Management administration module Check the list of supported operating systems in the System Requirements section of the download page for the Azure Rights Management Administration Tool.
Minimum version of Windows PowerShell: 2.0 Support for the Rights Management administration module is introduced in Windows PowerShell 2.0.By default, most Windows operating systems install with at least version 2.0 of Windows PowerShell. If you need to install Windows PowerShell 2.0, see Install Windows PowerShell 2.0.

You can confirm the version of Windows PowerShell that you are running by typing $PSVersionTable in a Windows PowerShell session.
Minimum version of the Microsoft .NET Framework: 4.0 If this is not already installed, you can download the full version of the Microsoft .NET Framework 4 (Standalone Installer).This version of the Microsoft .NET Framework is required for some of the classes that the Rights Management administration module uses.
Microsoft Online Services Sign-In Assistant 7.0 The Microsoft Online Services Sign-In Assistant is required for Azure Rights Management authentication.For more information, see Download Center: Microsoft Online Services Assistant for IT Professionals RTW.

Panorama Theme by Themocracy