Azure AD Connect – Connect Active Directory with Azure Active Directory

How to sync or connect Local Active Directory with Azure Active Directory (Office 365)

Follow this link having all details of Azure AD Connect : Azure AD Connect

4 points which I want to highlight are as follows:-

  1. Will the accounts which are disabled in local AD be synced to Office 365 ?
    Ans – Yes, the accounts which are disabled in the local AD will be synced to Office 365, however they will be in blocked state which means they will not be able to login in any O365 applications, unless they are enabled.
  2. How to merge two same accounts which are their on local AD as well as in Office 365?
    Ans – To merge the accounts, you need to update the “proxyaddress” attribute in Local Active Directory with the email address of the user which is available in Azure AD (Office 365). For updating the proxyaddress attribute, go to user properties and click on “Attribute Editor”. Follow the below convention to set the value:-
    SMTP:<email address>
    E.g. – SMTP:abc@xyz.com
  3. Is there a control panel of some type that allows us to force a synchronization of accounts and passwords, or is it set to a schedule?
    Ans – The software Azure AD Connect, will automatically schedule itself for every 30 mins of sync.
  4. Before we perform the live account sync, which password (on-premise or Azure) will take precedence?
    Ans – On Premise password will take precedence.

Hope this blogs helps many 🙂

Anonymous Site Access in Office 365 (SharePoint Online)

Recently, I have been asked a question about Anonymous Access in Office 365 (SharePoint Online). The question was – Can we give anonymous access to users within and outside the organization, so that just like any other Internet facing website, users will not enter their credentials and can directly see the SharePoint site contents ?

The requirement was – To share a Video Library/Document Library with all users (internal & external).

WOW. My first reaction and response to the question was “NOT POSSIBLE”. We can apply anonymous access in on-premise SharePoint Site/List/Library, but not in Office 365. There might be some third-party web-parts or sandbox solutions to deal with this, but there is no direct way to give anonymous access in Office 365.

To confirm my statement, I explored on Internet and found the same answers. We can only share list items with external users but cannot share a site/list anonymously. Also, I was sure that even Public facing sites cannot solve this purpose. Then I explored more on Public facing and Private sites in Office 365 and surprisingly, found the following facts from MS sites which details about Office 365 updates and plans:-

  1. Beginning May 1, 2017, anonymous access for existing sites will no longer be available.
  2. On September 1, 2017, when Microsoft deletes the public site collection in SharePoint Online, customers will no longer have access to the content, images, pages or any other files that reside on their public website. Before September 1, 2017, customers should make a backup copy of all their public website content, images, pages, and files, so they don’t lose them permanently.
  3. On March 31, 2018, Microsoft will delete all public sites that have been postponed.

I have listed only few updates and announcements from MS, the complete information, you can get on this site – Information about changes to the SharePoint Online Public Websites feature in Office 365

Finally, to conclude on anonymous access in Office 365, I will say that you can use external sharing features of SharePoint Online to share content with people outside your organization who do not have licenses for your Microsoft Office 365 subscription. However, that is just a sharing and not anonymous access, which means every user has to enter username and password to access the site resources. Share sites or documents with people outside your organization

Pros and Cons of Office 365

This article will help you to determine whether Office 365 is good or not for your organization, because moving to the Cloud can be a big decision for any business. Below are some of the Pros (advantages) and Cons (disadvantages) of using Office 365.

Pros

  1. Work Anywhere
  2. Email hosted in the cloud
  3. Easy and simple file storage and synching
  4. Easy Collaboration
  5. Always have access to latest products and applications (Always up-to-date)

Cons

  1. Less flexible infrastructure
  2. Subscription based
  3. Data privacy – All your private business data will live on Microsoft’s servers. This might not be a concern for everybody, but for certain use cases it might be even impossible (due to legal reasons) to have your data hosted outside your organization.
  4. If the internet is down, you may not be able to access work.
  5. It can be hard to keep up with changing feature set – The features in Office 365 do change fairly frequently. On one hand, you always have access to the latest and great versions.

Export-Import SharePoint Designer Workflow

Recently, I was working on SharePoint Online (Office 365) project and while publishing the workflows, the workflow was not getting attached to the specific list or library. I was developing SharePoint 2010 workflow in SharePoint Designer 2013. Also, the same workflows(s) needs to be applied to other sites in the same site collection. Then I tried exporting-importing the designer workflow using the below steps:-

Workflow (WF) Export and Import process :-

 Export Process:

Step 1: Export the source Workflow which you want to attach on another Site’s List.

Export 1

 

 

 

 

 

Step 2: Rename the downloaded file and append it with .zip extension.

Export 2

 

 

Step 3: Open Zip folder and delete “Workflow.xoml.wfconfig.xml”

Export 3

 

 

 

Step 4 : Rename the file again. Remove “.zip”

Export 4

 


Import Process:

Step 1: Import Source WF from destination site

Export 5

 

 

 

 

Export 6

 

 

 

Step 2: Specify List/library name

Export 7

 

 

 

 

Step 3:  Save (do not publish at this step)

Step 4:  Update approver list i.e. update the objects in your workflow which you want in your new workflow.

Export 8

 

 

 

Step 5:  Save and publish

Step 6: At this stage the workflow has no task and History list associated.

Export 9

 

 

Step 7: Close Designer because task/history list association and start options are disable.

Step 8: Open designer once again. Now these options are visible

Export 10

 

 

 

Step 9: configure WF settings and Save then publish.

NOTE: Microsoft Visio installation is not required for this export-import process.

Cascading drop-down in SharePoint OOTB list forms

In one of my recent project in SharePoint Online (Office 365), there was a requirement to implement cascading of drop-down. In my case, the two drop-downs are of Lookup Type getting values from a Master list. The two drop-downs were:-

Drop-down 1 – Event Type
Drop-down 2 – Event Category

cascading

 

 

 

 

The code used to implement the above functionality is:-

var userEntry = [];
var results = data.d.results;
//alert(JSON.stringify(results));
$.each(results, function(index,dataRec) {
userEntry.push({
id:dataRec.Id,
name:dataRec.Title
});//End of push
//alert(“In each userEntry”+ JSON.stringify(userEntry));
});//End of each
for(var j=0;j<userEntry.length;j++){
$(‘select[title=”Events Category Required Field”]’).append($(‘<option>’, { value: userEntry[j].id,text : userEntry[j].name}));
}//End of for

Microsoft is removing code-based sandbox solutions from SharePoint Online

Earlier in 2014, Microsoft announced that custom code in sandbox solutions would be deprecated https://blogs.msdn.microsoft.com/sharepointdev/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions/. On Monday, 29 July, 2016, Microsoft announced that it would be withdrawing support for code-based sandbox solutions in SharePoint Online and Office 365. New code-based sandbox solutions cannot be deployed and activated in SharePoint Online and Office 365 as of now, and existing sandbox solutions will stop working in the course of the next few weeks. This will pose a serious problem to the thousands of customers using sandbox solutions in their SharePoint online, since their solutions will just stop working.

Microsoft’s official announcement about switching off the sandbox solutions: http://dev.office.com/blogs/removing-code-based-sandbox-solutions-in-sharepoint-online

Recently, while working on SharePoint Online project, I faced the same issue when my sand-boxed wsp stopped working and other sandbox wsp’s were not activated. So, hurry up and change your sandbox solutions to AddIns, as suggested by MS.