Search This Blog


Monday, January 4, 2016

Understanding SharePoint Share Option at Site and Document Levels

The Pre-Conditions to enable External Sharing is that, External Sharing must be turned on for that Particular Site Collection. It can be turned on at the tenant level by the Office 365 Admin and then separately can turn on or off for every Site Collection. 

It is important to understand the below scenarios, when Share Option is clicked at the Site Level: 
  • When you are logged in as a User with Full Control Permissions Or you are present in the Owners Group, you can share your Site with both Internal Users as well as External Users; When such a User shares, he also will an option to select one out of 3 permissions levels: Owner, Edit or Read - so accordingly, the Owner user can assign permissions to any of these 3 permission categories. 
  • When you are logged in as a User with Contribute Permissions (Or you are present in the Members group), you can share your Site with both Internal Users as well as External Users). A Member user cannot select the Permission category for the Invited user. The user by default gets Member permissions only. 
  • When you are logged in as a User with Read Permissions (Or you are present in the Visitors group), you can share your Site with Internal Users, but the Permissions request are only sent to the Site Owner. The Site Owner then has to login, go to Site Settings -> Site Permissions -> Click on View Permissions Requests and Pending Invitations and then Approve or Decline the request. Once Approved, then, the respective User invited by the Visitor User will get the required permissions (Member / Contribute level and the Admin can change it after Approving also). A User in the Visitors group however cannot invite External Users                                                                                                                                                                                     External User Invitations also expire in 7 days.                                                                                   
 When a single document is shared, then Get a Link option appears (this does not appear when Site level Sharing is done) and behaves as below: 
  • When a Full Control or Member user shares this, then, he / she gets an option to send a link for both View as well as Edit 
  • When a Member user shares the document, then he / she gets an option to send a link only for View 

Saturday, November 21, 2015

Sharing in SharePoint 2013 - Explained well 

Friday, November 20, 2015

What’s new in Office 2016 for developers

As you’ve read, the new Office is here and for developers, this is an exciting time! The ability to insert add-ins into your documents, call new Office.js APIS, launch task panes inside your Office clients and run commands directly from the ribbon increases the productivity of your entire team! Add-ins now work across Office 2016 running on Windows, Office Online in your browser, Office 2016 on the Mac (Outlook currently) and Office on the iPad.
Office 2016 on Windows introduces some new extensibility features that will roll out over the other Office clients over time.

Add-in commands

Add-in commands provide ways to initiate specific add-in actions from the ribbon. This lets users access add-ins in a simple, intuitive and unobtrusive way. Because they offer increased functionality in a seamless manner, add-in commands allow developers to create more engaging scenarios and add-ins.
Add-in commands are declared in the add-in manifest in a new node called VersionOverrides. This node ensures backward compatibility because, in an environment that doesn’t support VersionOverrides, existing add-ins will continue to function as they did without add-in commands.
The screenshot below shows add-in commands on the ribbon at the right.
New in Office 2016 for developers 1

There is support for ribbon groups too as shown in this screenshot:

New in Office 2016 for developers 2

Run JavaScript using add-in commands

Add-in commands can also run JavaScript functions without further user input. In Outlook add-ins, you can perform actions such as track, remind me, print or for receiving more in-depth information from a service.

Launch task pane commands

You can use an add-in command button to launch a task pane to get more information from users. For example, the add-in may require changes to settings, or the completion of certain fields.
For details, check out “What UX shapes exist for add-in commands?
New in Office 2016 for developers 3

Theming capabilities for add-ins

You can use the new Theming APIs in your mail and task pane Office Add-ins to integrate your add-in with the Office theme. This widely requested feature allows your add-in to look and feel like the rest of the Office experience—regardless of the user’s preferences. To learn more, see Theme property. The recently announced Office UI Fabrictakes advantage of this new API.

New in Office 2016 for developers 4

Excel and Word Office.js functionality

The new Excel and Word Office.js APIs provide a variety of Excel and Word specific functionality related to the documents being collaborated on. Examples include populating content controls in Word or inserting formatted charts in Excel and are a result of UserVoice feedback from Partners and developers worldwide submitted. We’ve been working on a Snippet Explorer for both Word and Excel to let you browse through code snippets for common scenarios and learn how the new Excel and Word APIs work.
The example below highlights the Diet Tracker code sample that inserts rich charts using the Office.js APIs in Excel:
New in Office 2016 for developers 5

This screenshot highlights a Statement of Work Builder code sample that inserts rich formatted content into a document using Office.js in Word:

New in Office 2016 for developers 6

New in Office 2016 for developers 6

For more information on the new Word and Excel Office.js capabilities, read “Increase the productivity of users with enhanced Office.js APIs in Office 2016.”

My apps now are My add-ins

Office 2016 has been updated to reflect the platform name change from “apps for Office” to “Office Add-ins.” For details about the name change, see “New name for apps for Office and SharePoint: Office and SharePoint Add-ins.

New in Office 2016 for developers 7

Our partners

We continue to acquire more incredible partners in our Store. As mentioned in a previous blog post: Uber, PayPal,Evernote and Boomerang all have released add-ins that take advantage of these new development features.
New in Office 2016 for developers 8
PayPal task pane add-in paying a person directly within Outlook.
New in Office 2016 for developers 9
Boomerang task pane add-in inserting availability into the body of a mail.

New in Office 2016 for developers 10

Configure Free SSL with Exchange Server

Steps to configure Free SSL with Exchange Server

Wednesday, September 2, 2015

SharePoint Online Developer Resources including Migration from Server Object Model to Client Object Model

SharePoint Online Developer Resources

First up, on Transforming On-Premise Customizations to Online

Homepage: Office Dev Center

SharePoint Add-Ins - Apps for SharePoint are self-contained extensions of SharePoint websites that you create, and that run without custom code on the SharePoint server.

Note: The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see New name for apps for Office and SharePoint.

Office 365 APIs


Patterns and Practices

PnP is community driven open source project where Microsoft and external community members are sharing their learning's around implementation practices for Office 365 and SharePoint on-premises (add-in model). Active development and contributions happen our GitHub project under Dev branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications.

Notice that since this is open source community program, there’s no SLAs for the support what we provide from program. There is however highly active PnP Yammer group, where you can get fast support on any questions around the existing materials. If you are interested on getting more closely involved, please check the following guidance from our GitHub wiki: How to get started and contribute to Office 365 Dev PnP program?

Wednesday, August 26, 2015

SharePoint 2013 Permission Report: Check Access Rights for a Specific User

SharePoint 2013 Permission Report: Check Access Rights for a Specific User

I’m pretty sure that by now many of the SharePoint SME’s out there would have tried the “Check access rights script for a specific user” . Now if you’re new to this , please take a look at the link below to understand what this script is all about .It’s a very powerful tool with some limitations.  I happened to work with this script recently and listed below is my experience with this script .
  1. It doesn’t get really granular and looks for all the bits and pieces and retrieve the complete information we are looking for .For instance it can’t get the permission assigned on a list item and its just stops at the list level .In addition to that it doesn’t look for the security groups too. 
  2. The script takes atleast not less than 30 mins to 1 hour to run depending upon the size of the FARM and the contents it has as it has to go through all the contents in the FARM . So its better you run this script on a server which is properly scaled out .
  3. Another annoying fact about this script is , the final report displays the list of all the sites where the “NTAuthority\Authenticates users” group and the “Everyone” group is added . For sure every user in the domain would be a part of this group and its really annoying to see the  report displaying  all those results which we don’t really need . Moreover it would be  great if the result just displays the list of the sites where the user was explicitly added . 

Tuesday, August 25, 2015

Welcoming SharePoint 2016!

SharePoint 2016 Installation steps:

Summary of Enhancements and New features in SP2016:
Access Services 
Compliance features 
Customized web parts 
Document Library accessibility 
Durable links 
Encrypted Connections 
Fast Site Collection Creation 
Filenames - expanded support for special characters 
Hybrid in SharePoint 2016 
Identify and Search for sensitive content 
Image and Video previews 
Information Rights Management 
Large file support 
Mobile experience 
New controls for working with OneDrive for Business 
New Recycle Bin in OneDrive and Team sites 
Open Document Format (ODF) 
Project Server 
ReFS file system support 
SharePoint Search 
Sharing improvements 
Site Folders view 
Sites page pinning 
SMTP Connection Encryption 
SMTP ports (non-default) 
Web Application Open Platform Interface Protocol (WOPI)

SharePoint 2016 is starting to come up!

A short while ago, a public blog post was put up announcing the SharePoint Server 2016 IT Preview and the new cloud hybrid search preview for SharePoint Server 2013 and 2016. You can read it here.

Do take a few minutes to read through the post (it is a detailed read, covers several new areas in the IT preview including hybrid search/discovery, large file support, HTML5 support, improved provisioning capabilities etc.) and share the post with customers you are engaged with.

Announcing availability of SharePoint 2016 IT Preview and Cloud Hybrid Search

I am very happy to announce the release of the Public Beta for SharePoint 2016 On Premise. 
Over the past several months we have been working with both internal and external resources in the
SP16 TAP program testing the product towards this release and we are excited to present this out to the public.

This is the Public Announcement  (Please share this out with your external customers and collegues)
You can find the download Here

Additional Information
Background Links to SharePoint 2016 On Premise (What’s New for IT Professionals Ignite Session)