Tag Archives: SharePoint

SharePoint Online Improvements

Today Mark Kashman, the senior product manager on the SharePoint marketing team, announced new improvements rolling out to SharePoint Online.  Below is a quick summary of the changes:

  • Improved file upload experience: increased file upload limit from 250MB to 2 GB and expanded support for a broader range of file types.
  • Increased Site collection and list lookup limits: increased site collection limit from 3,000 to 10,000 and list lookup threshold to 12 lookups.
  • Improved self-restoration: increasing recycle bin retention duration and turning versioning on by default for new SkyDrive Pro libraries.

Read the full announcement here.

SharePoint 2013 in Windows Azure

Today a co-worker forwarded an interesting video to me that I thought I would share.  This video shows how a SharePoint 2013 infrastructure can be deployed in Windows Azure and can quickly scale to support additional workload.   You can checkout the performance of the SharePoint 2013 site running on Azure by visiting http://con-web.cloudapp.net/

Could your organization benefit by hosting SharePoint in Azure?

Cross-product solutions with Exchange, Lync, and SharePoint Server

The Microsoft Office Division is investing in documentation to help customers deploy cross-server solutions that include Exchange 2013, SharePoint 2013, and Lync 2013.   The first Visio diagrams being made available include:

  • Server-to-server authentication

  • High resolution user photos

  • Unified contact store

  • Site mailboxes

  • Exchange task synchronization

  • Lync presence in Outlook

  • Voicemail

  • Check out the new diagrams on TechNet.

    Free Download: SkyDrive Pro Client

    When SharePoint 2013 and the new SharePoint Online was released there was a new capability included called SkyDrive Pro.   This capability is similar to the consumer SkyDrive solution, however, it is based upon SharePoint and can be managed by the enterprise organization.

    Up until now to use SkyDrive Pro you needed to deploy Office 2013 on the desktop.  Although many customers have Enterprise Agreements or are Office 365 customers, they are just not quite ready to deploy Office 2013.   This means that they can’t take advantage of the SkyDrive Pro capability.

    Recently Microsoft released a free standalone SkyDrive Pro client for Windows that can be installed side by side with previous versions of Office.

    Visit the Microsoft Download Center to learn more and to download the SkyDrive Pro Client.

    SharePoint 2013 Development Overview

    SharePoint 2013 and SharePoint Online provides a new modern application development model. This new model provides a scalable way to build SharePoint solutions using standards based technologies.

    Modern SharePoint apps are built in a way that allows the organization to choose how and where to host the apps. This model also makes it much easier for an organization to move between SharePoint on-premises and SharePoint Online.

    To help explain the different development options I have created a SharePoint 2013 development overview slide deck.  The intent of this deck is not to teach a person how to do development, but instead to outline the different development models available.  With this information an organization can make a well informed decision on how to approach custom development with SharePoint.

    Get Started Building Apps for Office 365, Office 2013 and SharePoint 2013

    If you are interested in developing apps for Office 365, SharePoint 2013 or Office 2013, grab the new Office Developer Tools for Visual Studio 2012 here:  http://www.microsoft.com/visualstudio/eng/office-dev-tools-for-visual-studio

    Once installed you will find two new project templates in Visual Studio;  App for Office 2013 and App for SharePoint 2013.  These two templates provide the necessary plumbing to help you get started building new apps quickly.

    Building custom solutions using SharePoint 2010 required a local installation of the server software.  The new app model for SharePoint 2013 has changed the way developers will build out their environment.  Instead of using a local installation of SharePoint 2013, app developers can use a remote SharePoint 2013 server or SharePoint Online tenant.  This new capability reduces the complexity of the developer workstation and reduces the amount of memory and software that needs to be installed.  MSDN has a great article explaining how to setup a development environment for building apps for SharePoint on Office 365.  I would recommend that developers build solutions using the new SharePoint app model instead of the traditional server-side object model based farm or sandboxed solutions.

    Server-side object model based farm or sandboxed solutions can still be created if necessary. If you plan to build solutions using the server-side object model then you will still require a local installation of SharePoint 2013.   Because of this requirement, the developer workstation will need at least 16GB of RAM;  24GB is recommended.  Steps to setup a local instance of SharePoint 2013 for development can be found on MSDN here

    Organizations that are using SharePoint 2013 on-premises can use their SharePoint instance for development.  Steps for configuring your development environment and your on-premises SharePoint environment for creating SharePoint apps can be found on MSDN here.

    Microsoft has provided very good documentation and samples for developers to learn how to build apps using SharePoint 2013.  I would recommend starting with the article titled Build apps for SharePoint.  Additional documentation and samples can be found at http://msdn.microsoft.com/sharepoint

    Don’t forget that apps you create for SharePoint 2013 can be published to the SharePoint store where you can make money!   You can learn more about publishing your apps by reading the MSDN article titled Publish apps for SharePoint.

    Leave me a message below or using the Contact Me! link above if you have published a SharePoint app in the store.  I am very interested to see what solutions are created.

    New Visio Stencils for Office 2013 Server Products

    Microsoft has made new Visio stencils available for Exchange 2013, Lync Server 2013, and SharePoint Server 2013.  Download links are below:

    This stencil contains more than 300 icons to help you create visual representations of Microsoft Office or Microsoft Office 365 deployments including Microsoft Exchange Server 2013, Microsoft Lync Server 2013, and Microsoft SharePoint Server 2013.  Download here.

    This stencil contains Exchange 2013 specific icons to help you create visual representations of Microsoft Exchange 2013 deployments, including on-premises, hybrid, and Office 365. Download here.

    SharePoint 2013 + Exchange 2013 = Site Mailboxes

    When an organization deploys the new Office 365 or chooses to deploy SharePoint 2013 and Exchange 2013 on-premises they can use a new feature called a site mailbox.

    A site mailbox is a shared Exchange mailbox that is associated with, and managed by a SharePoint site. A site mailbox provides teams a more integrated way to capture not only documents but also team communications.

    Creating a new site mailbox is as easy as creating a list or document library.  Within the new SharePoint 2013 Site Contents section an option exists to add a new app.

    All lists, libraries and other applications are now called “apps” within SharePoint 2013.  Clicking on the add an app option will present you with the standard SharePoint list and library templates along with any other additional applications that have been installed within the SharePoint environment.  One of the new applications is called a Site Mailbox.  Choosing this item will create an Exchange 2013 mailbox and associated it directly with your SharePoint site.

    Once the mailbox is fully provisioned, which may take several minutes, any contributor on the SharePoint site will have access to the new shared mailbox.  When the provisioning of the mailbox is completed, each of the contributors on the site will receive an email message with information about the new site mailbox, including its email address.

    After creation a link to the site mailbox will be automatically added to the quick launch navigation bar on the SharePoint site.  Clicking on the link will launch the site mailbox using the Outlook Web Application.  Contributors of the SharePoint site will be able to read, reply to, or create new email messages directly from the site mailbox.   Email messages that are sent using the site mailbox will be kept in the site mailboxes sent items folder, however, the from address will always be the user who sent the email and not the site mailbox address.

    Site contributors that are running Outlook 2013 will automatically see the new mailbox show up in their Outlook client giving them quick access to both the site mailbox and the document library on the site.  Outlook provides that one single client access into both email content and documents stored within SharePoint.

    In the image above, you can see that Karen B. has a primary mailbox in Outlook 2013 and a Northwind Traders site mailbox.  From that site mailbox she can quickly have access to both the emails and documents located on that site.  If Karen B. is removed from having contributor permissions on the SharePoint site, she would also lose access to the site mailbox.   As a result, the Northwind Traders mailbox shown in her Outlook 2013 client would also automatically be removed.

    When the SharePoint site is deleted a process will ensure that the site mailbox is also deleted from Exchange.  If you choose to use a site mailbox you will want to think about both the data lifecycle for the SharePoint content and Exchange mailbox content.

    The tighter integration of Exchange with SharePoint is providing new and exciting collaboration capabilities across the Microsoft productivity platform.  Learn more about Site Mailboxes on TechNet.

    SharePoint 2013 using Azure ACS – Part 2

    It has been some time since I wrote part 1 of this post and I was hoping that I would have part 2 completed and online within a week.  Due to a very exciting announcement from one of my customers I have been very busy and was unable to get back to completing this article.   I also have been distracted with the new multiplayer game PlanetSide 2 and my old standby World of Warcraft (yeah… I am one of THOSE people).

    After reviewing a previous article I wrote regarding Azure ACS and SharePoint 2010, I have decide to not complete my article related to SharePoint 2013.   The reason is that the second part of this series is exactly the same in SharePoint 2013 as it was in 2010.  The only change that has occurred is that the sign-in URL for Azure ACS has changed.   Therefore, I am going to reference the original article below and then highlight the change that need to be completed in order to complete the configuration for SharePoint 2013.

    To complete the Azure ACS SharePoint 2013 configuration start with step 1 located on this previous Azure ACS article.

    In step 3, you will need to make a minor modification to the PowerShell script.  There is a PowerShell variable called $signInUrl that needs to be set to “https://<namespace>.accesscontrol.windows.net/v2/wsfederation” where <namespace> is the namespace you defined in step 6 in part 1 of this article.

    Complete the rest of the steps in the Azure ACS article to configure a SharePoint 2013 web application to use Azure ACS for authentication.