• Login to SharePoint Online site collection
• Navigate to Site Settings --> Site Permissions --> Access Request Settings

• Click on Permission level from Site Settings
• I choose Edit Permission level for this testing (Edit is the permission level mapped to Members group by default).

• Uncheck “Browse User Information – View information about users of the website” which disables Use Self-Service Site Creation and Edit Personal User Information by default.

• Tested the permission with user AllieB who is part of the Site Member group

• When AllieB clicks on Share from the top Ribbon, she gets access denied as shown below.

• When AllieB clicks on Share from Document library she get the same access denied error. This behavior is same while AllieB uses Share from Document more option.

This way, you can restrict share button for users with read and write :)

Hope this helps !..

Disclaimer:

Do try this on a test environment before implementing it on a Production site.

Note:- You may skip configure / Register Managed account steps, if you already have the account registered in your farm.

Browse to your SharePoint Central Administration.

Navigate to Security from Quick launch.

Click on Configure Managed accounts under General settings as shown below.

 Click on Register Managed Account to add the Service account which you would Change to.

Fill in the service account information in the Register managed Account.

 Now its time to change the Service account for the Web Application.

Navigate back to Security from Quick launch shown below and click on Configure Service accounts

In the Service Account page, select the Web Application for which you would need to change

Select the appropriate service account and hit OK.

 We are all set!!!!…….. OOPS, 1 last think... Don’t forget to do an IISReset.

It worked like a charm. J

************************************************

Disclaimer. :- I had tested this scenario in my test lab and it worked just fine, I request you to try it in your test / dev environment before implementing in your Production environment.

***************************************************************************************************************************************************************************************************************

Below is the configuration i tested with.

• Windows Server 2012 R2 Domain Controller
• Windows 8.1 Client machine

I followed the below step.

Login to your Domain Controller.
Open your Group Policy Management tool and edit Default Domain Policy.

Navigate to “Administrative Template  à Windows Components à SkyDrive

Edit “Prevent the usage of SkyDrive for file storage” and set the state to “Enabled” “

Ensure, the Group Policy changes are update to all the client machines.

Now when your client starts the SkyDrive App, he / she will get the below information.

 Disclaimer

*************

The above information is from my test lab, and you can use this information to reproduce and test it in your environment. 

Recently, i worked with a customer who wanted to control (allow / block) devices which are connecting to his Exchange Online and was looking for an Out of the box solution. To demonstrate the power of Exchange Online MDM, i followed the below steps.

1.      Login to O365

2.      Navigate to Exchange Online Admin Center (Admin -> Exchange)

3.      Click on Mobile from the left navigation

4.      Under Exchange ActiveSync Access Settings click Edit.

a.      Select Quarantine – Let me decide to block or allow later

b.     Add a Quarantine Notification email message, to send a notification.

c.      Provide a Custom text message, if you would like to place any policy / note information.

5.      Now when a user tries to access email from his mobile Outlook, it automatically places the device under Quarantine Devices.

             a.      The requester will receive an notification email, with the custom message which was included in the earlier configuration 4(a)

             b.      Send’s an email to Quarantine Notification email address for approval.

6.      Exchange administrator can allow / block this / these model devices.

             a.      Admin can allow access only for that device / all similar devices.

             b.      This can be done by creating as shown below.

7.      Once the device is allowed / blocked with the rule, you will find it under Device Access Rules, as shown below.

8.      If in case, you want to change these access rule for the applied devices, use the Device Access Rules

Hope this helps you.

Cheers...

I was able to populate the containers, but when i say Save / OK it gave me the below error

 "There was no endpoint listening at https://localhost:5725/ResourceManagementService/MEX that could accept the message. This is often caused by an incorrect address or SOAP action." 

Tried creating a new UPSA, this time it gave me an error UPSA Sync Services is not started.

Quickly navigated back to Service on Server and found it to be running.

Gave a shot by stopping and starting the services, there you go... it worked like a charm. 

Thought of writing the step-by-step process, which might be helpful for some of you.

Note: -  

         a.  You can install ADFS and DirSync on the same box, IT IS NOT RECOMMENDED BY MICROSOFT

         b.  You can’t install DirSync on a Domain Controller.

 Installing and activating DirSync for your Office365 Portal.

 1.      Login to your Office365 Portal with Tenant admin credentials. (The username and password which you provided while provisioned your Office365 Portal)

2.      On the Admin page, in the left pane, under Management, click Users, and then click setup next to Active Directory® synchronization.

3.      Scroll down to step 3 and 4, as shown below in the screen capture.  

                    i.     Activate DirSync for your Office365 Portal from step 3 (This might take a while to get activated)

                   ii.      Download DirSync 64 Bit from step 4

4.      Run the downloaded DirSync.exe

5.      Click on Next button in welcome screen

6.      Accept the License Terms and Click Next

7.      Click next on the “Select Installation Folder” if you don’t want change the location.

8.      This Installs DirSync in your local machine

9.      Click Next to start the DirSync Configuration wizard.

                   a.   Ensure the “Start Configuration Wizard now” is checked.

10.  Click Next on the “Welcome Configuration wizard”

11.  Enter your Office365 Tenant admin account and password and click next.

12.  Enter your local Active Directory account who is part of enterprise admin group.

13.  If you have Exchange Server on-Premise and planning to implement a hybrid configuration, then select “Enable rich coexistence” and click next.

                 i. Nothing to worry if it is greyed out for you, which means you don’t have on Exchange On-Premises deployed.

 14.  Uncheck the Synchronize directories now from the DirSync Finish window and click Next.

 Configure OU level filtering for Office365 directory synchronization.

1.      Logged in to your Domain controller

2.      Created an OU (Organisational Unit) from your AD (Active Directory)

                 a.       In my case I named it “DirSync”

3.      Move all those users you want to sync, to that DirSync OU.

4.      From your DirSync Server navigate to <Drive>\Program Files\Microsoft Online Directory Sync\SYNCBUS\Synchronization Service\UIShell

5.      Double click on miisclient.exe

6.      This opens a console something similar to the below screen capture 

 7.      In Identity Manager, click Management Agents, and then double-click SourceAD.

8.      Click Configure Directory Partitions, and then click Containers, as shown in the below screen capture.

9.    When prompted, enter your domain credentials for the on-premises Active Directory forest.

10.  In the Select Containers dialog box, clear the OUs that you want skip from syncing to Office365, and then click OK. Something similar to below screen capture.

11.  Click OK on the SourceAD Properties page.

12.  Perform a full sync: on the Management Agent tab, right-click SourceAD, click Run, click Full Import Full Sync, and then click OK.

If you would like to know more about DirSync filtering refer the TechNet article here

13.  You can also force run DirSync using the following PowerShell command.

                       i.      From your dirsync server open PowerShell console as Administrator

                       ii.      Navigate to  “C:\Program Files\Microsoft Online Directory Sync”

                       iii.      Run .\DirSyncConfigShell.psc1

                       iv.      Now execute Start-OnlineCoexistenceSync commendlet.

14.  To confirm the sync job, open your event log and look for Event ID’s 1 & 2.

                        v.      Event ID 1 says If configuration Import started

                        vi.      Event ID 2 says if configuration Import has completed.

15.  To verify from Office365 Portal

                        vii.      Login to your Office365 Portal with Tenant admin credentials. (The username and password which you provided while provisioned your Office365 Portal)

                        viii.      On the Admin page, in the left pane, navigate to Users.

                         ix.      And you can verify the Last Synced status next to Active Directory® synchronization as shown below

16.  Verify only the Filtered users are populated to Office365 from office365 user management.

Note:-

Filtering configurations applied to your directory synchronization instance aren’t saved when you install or upgrade to a newer version. If you are upgrading to a newer version of directory synchronization, you must re-apply filtering configurations after you upgrade, but before you run the first synchronization cycle.

For testing purpose, I tried installing SharePoint 2013 Preview on the same Windows Server 2012 Release Candidate box and it just worked.

With that, I tried installing Windows Server 2012 Standard and SharePoint 2013 on it, hurray !!! everything worked.

• To add a new domain and federate with your on-premise ADFS server.
• To federate your existing Office365 domain.  

Requirement

• You need to run this script from the ADFS box which will federate with Office365.
• Basic idea of how to add a TXT entry to your hosting provider, for more info refer https://onlinehelp.microsoft.com/en-us/office365-enterprises/gg584188.aspx .

Quick introduction about this guy.

He collects the following information from you:

• Office365 credentials
• Domain Name
• Your confirmation to know: if you are federating with a domain name which is already added to your Office365 portal or add and federate a new domain to office365.
• Finaly a log file location for an error output.

Things you should be aware:-

• This script does the domain verification, once the added TXT record is replicated.
• Domains added using this script can be verified only with New-MsolFederatedDomain –DomainName <Domain Name> command
• The domain verification might fail due to TXT recort replication, if so follow this KB Article and run New-MsolFederatedDomain –DomainName <Domain Name>

 Note: - With my experience, I had to wait for 15-30 mins for the DNS replication.

I recommend you to download the attached .ps1 file to avoid any typo's. 

##################################################################################

#Created by KannaGanesh On 10-15-12

#This script helps you to federated a new / existing
domain with Office365 portal

##########################################################################################

write-host "This script helps you to federate a new
/ existing domain with Office365"

$cred = Get-Credential

$Domain = Read-Host "Provide your domain name that will be added to your Office365Portal"          # this reads your Domainname that needs to federated with your Office365 subscription

$logfile = Read-Host "Get a logfile path"

Connect-MsolService -Credential $cred                 #Provide your microsoftonline credentials <admin@domain.microsoftonline.com>

$confirm = Read-Host "Please hit "S" to federate your existing Office365 domain / hit "N" for adding and federating a new domain with Office365" 

If ($confirm -eq "S")

{

Convert-MsolDomainToFederated -DomainName $Domain # This
converts your existing domain to federated

}

else

{

New-MsolFederatedDomain -DomainName $domain      # This line adds your domain to Office365 portal

write-host "Please note the DNS entry might take
some time for replication" -foregroundcolor Red -backgroundcolor white

Read-host "Hit enter once DNS entries or done"                 

New-MsolFederatedDomain -DomainName $domain -errorvariable e; # This line validates your domain verification

Write-Output $e > $logfile

If($e -ne $null)

{

Read-Host "Hit enter once you are ready to verify your domain"  # This gives you a chance of verifiying the added domain again.

New-MsolFederatedDomain -DomainName $domain -errorvariable a -ea silentlycontinue -wa silentlycontinue;

$date = (get-date).ToString()

Write-Output $a $date | out-file $logfile -append  # If the verification failed, then it writes an output to log file

If($a -ne $null)

{write-host "Your Domain verification failed, pls verify the txt record and run New-MsolFederatedDomain -DomainName <Domain Name> for successfull completion of federation" -foreground "White" -background "Red" ;

write-host "for more info check the log file @ $logfile"}

# This write-host command tells you how to validate your domain after fixing the DNS record

else

{write-output "Congrats you have successfully configured federation"

#################################################            THE END                    ###############################################

How to run this script:

• Login to your ADFS server
• Open MSOnline Shell as administrator
• Run set-executionpolicy unrestricted from MSOnline shell
• Now it’s time to run the script .\office365federation.ps1
• Provide your office365 Credentials.
• Now you will be prompted for your Domain name, that will be federated with Office365.
• Choose your option, if you need to federate an existing domain / add & federate a new Domain
• Based on your selection the script federate / add & federate a domain to Office365
• If it is only the federation of an existing Domain, then this script does the federation and ends there.
• If it is for adding & federating a new domain to Office365 then it follow the below steps:
• Adds the domain to your Office365 tenant
• Provides the TXT record that needs to be added with your provider
• Once the record is added and ready for replication, An ENTER key will help the script to verify your domain.
• If the verification failed for the 1^st time, it prompts you to validate the replication of TXT record that was added and then confirm by hitting an ENTER key.
• If the TXT record was replicated, your verification will be completed by now.
• Else, you will have to run New-MsolFederatedDomain -DomainName <Domain Name> for verifying the domain once the TXT record replication is done.
• Once the script is executed set it back to Restricted, using

Hope this helps you.  

Office365Federation.ps1