Mar 09
OneDrive for Business – Shared by me view

A new view is being deployed on OneDrive for Business to help you identify all content you have shared.

This new view is simply called Shared by me (as you would imagine Smile)

To access this view, logon to your OneDrive for Business space using a web browser and reach the Shared view

On top you will see 2 views: Shared with me and Shared by me


Then, you can directly manage the access by selecting the shared content and click on the Manage access button

image image

Mar 09
Office 365 – IMPORTANT NOTICE - Office documents will now open in Edit mode in the browser

This is going to be a potential issue.

An update is being deployed (already done for First release tenant) which is going to open Office document in Edit mode when you use the web browser (the Office Online license).

You need to communicate to your end-users to be careful when opening an Office document with the web browser (and inform your support team).

Mar 05
Teams – You can recover deleted channel from Teams

After allowing administrator to recover deleted Teams, Microsoft Teams has been updated and now allows you (and I mean end-user here) to recover deleted Teams channel for up to 21 days after the channel has been deleted.

To recover a channel, the Teams owner needs to go to the Teams settings (Manage Team)


Then you go to the Channels tab and open the Deleted group to select the channel to recover and click on Restore


Finally confirm the recovery


Et voilà your deleted channel is recovered

Mar 01
Teams – You can now invite non corporate user as guest

You may already know it has been possible to invite external users to your Microsoft Teams but this was limited to corporate account – meaning external users with Office 365 account.

Now, this has been finally extended to allow you to invite also external users with Microsoft Account.

NOTE please note the updated feature is being rolled out with an estimated completion date at the end of March.


Off course, this means you already have enable Guest access from your Office 365 Admin portal (Settings\Services & add-ins\Microsoft Teams and turn on the Guest access)


Feb 22
Office 365 – Naming convention for Office 365 Groups is available in preview

We already had a group naming policy available for Exchange security mail-enabled or distribution groups BUT this did not apply to Office 365 Group name.

Starting today, and in preview, a group naming policy is available for Office 365 Groups; this will apply to Office 365 Groups AND Teams

NOTE this functionality requires to have Azure AD Premium and the Azure AD Preview module (version or later)

To implement Office 365 Groups naming policy, you need to connect to your Azure AD with PowerShell and the use the following commands

  • To install the Azure AD Preview module, run the following command Install-Module AzureADPreview from a PowerShell prompt launched with the run as administrator

As usual with the Install-Module command, you  may be prompted to install NuGet and trust the repository

NOTE you may need to uninstall previous version of the Azure AD modules or Azure AD Preview modules prior to install the latest version


  • Once installed, connect to your Azure AD Tenant with the command Connect-AzureAD


Get Current Office 365 Groups Naming Settings

  • To get the existing naming convention settings, run the commands $Setting = Get-AzureADDirectorySetting -Id (Get-AzureADDirectorySetting | where -Property DisplayName -Value "Group.Unified" -EQ).id and then $Setting.Values


Define Office 365 Groups Prefixes/Suffixes

  • To define names prefixes and/or suffixes run the following commands $Setting["PrefixSuffixNamingRequirement"] = <your prefix / suffix settings>, like $Setting["PrefixSuffixNamingRequirement"] = “Grp_[Department]_[GroupName]_[Country]", and then Set-AzureADDirectorySetting -Id (Get-AzureADDirectorySetting | where -Property DisplayName -Value "Group.Unified" -EQ).id -DirectorySetting $Setting

NOTE you can use either a string and/or user attribute between brackets []. Using user attributes will automatically fill the ‘gap’ with the value from your Azure AD (or your Active Directory if you are using directory sync). The [GroupName] section will be filled with the value provided by end-user during the group creation


Define Office 365 Groups Block Words

  • To define a list of blocked words, use the commands$Setting["CustomBlockedWordsList"]=”<your blocked word comma separated list>”, like $Setting["CustomBlockedWordsList"]=”Payroll,CEO,HR”, and then Set-AzureADDirectorySetting -Id (Get-AzureADDirectorySetting | where -Property DisplayName -Value "Group.Unified" -EQ).id -DirectorySetting $Setting

Disable the setting

  • If you want to disable one of these settings, just set the value to $null, like $Setting["PrefixSuffixNamingRequirement"] = $null and run the set command Set-AzureADDirectorySetting -Id (Get-AzureADDirectorySetting | where -Property DisplayName -Value "Group.Unified" -EQ).id -DirectorySetting $Setting


End-User Experience

The policy will then be applied and available from any client used to create new Office 365 Groups (or Teams), like Outlook on the Web (OWA), Outlook 2013/2016 on Windows or Outlook for Mac.

NOTE this seems not applicable if an Office 365 administrator is creating the group from Office 365 Admin portal or Azure Portal


Feb 22
Office 365 – You can simulate an attack on your Office 365 (preview)

UPDATE March 10, 2018 – I have been informed the invitation code to join the preview portal is no longer valid

Even if we all know Office 365 is quite secure by design, you may want to evaluate by yourself the security level of your tenant.

While you already have the Secure Score ( functionality available, this will basically just help you to identify best practices to implement.

Today, you will be able to simulate an attack against your Office 365 tenant (in preview)

With Attack Simulator, admins can launch simulated attacks on their end users, determine how end users behave in the event of an attack, and update policies and ensure that appropriate security tools are in place to protect the organization from threats.  This preview of Attack Simulator includes three attack scenarios:

  • Display Name Spear Phishing Attack: Phishing is the generic term for socially engineered attacks designed to harvest credentials or personally identifiable information (PII). Spear phishing is a subset of this attack type which is targeted, often aimed at a specific group, individual, or organization.  These attacks are customized and tend to leverage a sender name that generates trust with the recipient.
  • Password Spray Attack: To prevent bad actors from constantly guessing the passwords of user accounts, often there are account lockout policies.  For example, an account will lockout after a certain number of bad passwords are guessed for a user.  However, if you were to take a single password and try it against every single account in an organization, it would not trigger any lockouts.  The password spray attack leverages commonly used passwords and targets many accounts in an organization with the hope that one of the account holder uses a common password that allows a hacker to enter the account and take control of it.  From this compromised account, a hacker can launch more attacks by assuming the identity of account holder.
  • Brute Force Password Attack: This type of attack consists of a hacker trying many passwords or passphrases with the hope of eventually guessing correctly. The attacker systematically checks all possible passwords and passphrases until the correct one is found.

Before starting, as usual there are some prerequisites:

  • You need to have Office 365 Threat Management
  • You are using Exchange Online to host your mailboxes; at this time, the simulation is not running for on-premises Exchange. Maybe this will come as with now have Threat Management available for on-premises (ATA)
  • You are using Office 365 MFA
  • You need to register to the preview portal ( by using the invitation code (invitation code no longer valid) if you want to provide feedback and influence future features (you will join the Office 365 Universal Preview)

Once all done, you can start Smile

  • Logon to your Office 365 Compliance Center and reach out the Threat Management\Attack simulator section


  • Then choose the attack scenario you want to run; for each you can get some details by using the Attack details link; this link will also gives you attack history


  • To start an attack scenario, just click on the Launch attack button and complete some configuration; the settings depend on the attack scenario


  • Then the reports (is currently, I think this should/will change in the future) are available in the attack details history



Below the phishing email received and the page were users are redirected when you try the Phishing Attack scenario AND your users click on the embedded link


Feb 22
Intune – Enable Windows Redeployment from logon screen

Starting with Window 10 build 1709, it is possible for administrators to re-initialize Windows 10 devices to remove personal files and settings and revert the device to an original state, while keeping the device enrollment.

Enable the policy

To make Windows Automatic Deployment available from the logon screen, you must first enable the policy; which can be done either with Intune (or any MDM supporting CSP) or with a Windows Configuration Designer package.

  • Logon to your Azure tenant with an administrator account and access your Intune blade


  • Then access the Device Configuration blade to create a new Windows 10 custom profile


  • Then name the new profile and set the configuration as below
    • OMA-URI: ./Vendor/MSFT/Policy/Config/CredentialProviders/DisableAutomaticReDeploymentCredentials
    • Data type: Integer
    • Value: 0 – (the default value is set to 1 which means disabled)


  • Finally assign the new policy to devices or group of devices



Trigger the redeployment

Once the policy has been created and deployed, wait to ensure the policy is applied to the device(s) you want to reset

  • You can check the registry key

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{01A30791-40AE-4653-AB2E-FD210019AE88} and check the value of the Disabled value which need to be set to 0


  • Then at the logon screen use the keys combination Ctrl + Windows + R to open a new custom login page to sign in with an administrator account


  • You can also get the Automatic Deployment button available from the locked screen after hitting the Sign In options


  • After entering your local administrator account; you can use either a local account or a corporate account defined as local admin (see the

    Additional local administrators on Azure AD joined devices available from the Azure AD\Devices\Devices settings blade), Windows 10 will be redeployed


  • Once completed, Windows is ready to go; already joined to Azure AD (as it was before); if the device needs to be connected to WiFi, you will be requested to select the WiFi network to connect to first


Feb 19
Azure – Hybrid Cloud Print service

Hybrid Cloud Printer Service is a new feature available on Windows Server 2016 allowing you to setup a print server/service available not only to AD Joined devices but also to Azure AD Joined devices.

Using corporate print servers while using an Azure AD Joined device can be challenging for both end-users and IT staff.

With this new feature, any Azure AD Joined devices will be able to easily setup and use corporate printers, wherever they are.

To implement this solution, you need to following requirements – in addition of the obvious ones which are Azure AD and Active Directory:

  • Azure AD Connect – installation and configuration not covered in this post
  • Intune
  • Azure AD Proxy – activation, installation and configuration not covered in this post
  • Azure Web Application

Bear with me as this is not a simple and easy process – including the printers publication. Hopefully this will be improved in a future release/update.

This is an interesting functionality but clearly still lot of work


Enable Hybrid Cloud Print feature

On a Windows Server 2016, enable the Hybrid Cloud Print feature either using PowerShell (don’t forget to use the Run As Administrator); you may be asked to install NuGet and trust the online module repository

  • Enable the Windows Server Role Print Server
  • Install-Module -Name PublishCloudPrinter
  • Import-Module PublishCloudPrinter


  • Then you need to configure the connection to your Azure Active Directory by launching the CloudPrintDeploy.ps1 script located in the C:\Program Files\WindowsPowerShell\Modules\PublishCloudPrinter\ folder

This will enable IIS serve role with Asp.Net

CloudPrintDeploy.ps1 -AzureTenant <Domain name used by Azure AD Connect> -AzureTenantGuid <Azure AD Directory ID>; where the Azure tenant is the <your tenant name> URL and the tenand GUID is obtained from the Azure AD properties (Directory ID)


  • You then need to configure SSL on the IIS web site either by using a self-signed certificate or by using a certificate generated by a CA. As the certificate needs to be trusted by the client, it is recommended to use a public CA – or you internal CA if you have deployed your CA certificate to the Azure AD Joined device (which can be done by using Intune)


  • Next, you need to install SQLite package using the following PowerShell commands

Register-PackageSource -Name -ProviderName NuGet -Location -Trusted –Force

Install-Package -providername nuget


  • Copy the SQLite DLL’s from each SQLite subfolder located in C:\Program Files\PackageManagement\NuGet\Packages to the Mopria Cloud Service virtual directory (C:\inetpub\mopriacloudservice\bin)

System.Data.SQLite.**Core**.x.x.x.x\\lib\\net46\\System.Data.SQLite.dll copied to the bin directory
System.Data.SQLite.**Core**.x.x.x.x\\build\\net46\\x86\\SQLite.Interop.dll copied to the bin\x86 directory
System.Data.SQLite.**Core**.x.x.x.x\\build\\net46\\x64\\SQLite.Interop.dll copied to the bin\x64 directory
System.Data.SQLite.**Linq**.x.x.x.x\\lib\\net46\\System.Data.SQLite.Linq.dll copied to the bin directory
System.Data.SQLite.**EF6**.x.x.x.x\\lib\\net46\\System.Data.SQLite.EF6.dll copied to the bin directory


  • Then edit the web.config file located in C:\inetpub\mopriacloudservice to replace the value set for newVersion with the actual installed one (in my case when writing this post,the version registered in the web.config file was and the installed one was


  • Finally you need to create the SQLite database with a command lien.The database which will be located in C:\C:\inetpub\mopriacloudservice\Database using the SQLite management tool (SQLite Tools) available at

sqlite3.exe MopriaDeviceDb.db ".read MopriaSQLiteDb.sql"


  • Edit the NTFS permissions on the MopriaDeviceDb.db file located in C:\inetpub\wwwroot\MopriaCloudService\Database to grant read and write permissions to users/groups being authorized to publish shared printers


Create the Azure Web Applications

3 Azure Web Applications are required to implement the hybrid cloud printer service – 2 as web app/API and 1 native:

    • one web app/API acting as the print service proxy
    • one web app/API acting as the print service discovery service
    • one native app acting as the print service

    For this post, I’m assuming you already have deployed Azure Application Proxy; if not you can check this post

    • From Azure administration portal, go to the Enterprise Application\All applications options of your directory and publish On-Premises application


    Recommendation I would recommend to set the Visible to users option to No as well as the User Assignment Required option set to No after publishing the applications; this will ensure the applications will not be displayed on the Azure Application Control Panel which could cause some trouble as the end points are designed to interact with end-users through the web browser


    Recommendation while you can keep the default External URL, it is recommended to customize it by either shorten it or use your Internet domain. If you use your Internet domain, do not forget to create the required CNAME and also use it when generating the IIS certificate (used previously). You will then have to upload this certificate


    IMPORTANT NOTE if you perform any update on the Azure Web Applications, double check the Home page URL is still as defined below.

    Hybrid Cloud Discovery Endpoint Web Application 

    • Name: name the application has you wish; as usual use an understandable name, like Hybrid Cloud Print Service Discovery
    • Internal URL: this is your internal print server (something like https://serverfqdn/mcs/)
    • Pre authentication method: Passthrough


    • Once the discovery application has been created, edit it to update the App ID URI to http://MopriaDiscoveryService/CloudPrint


    • Then apply the required permissions by accessing the Required permissions blade to grant Sign in and read user profile permission (if not granted) and then apply by clicking on the Grant permissions


    • Edit the Home page URL to be set as http://MopriaDiscoveryService/CloudPrint



    Hybrid Cloud Proxy Service Web Application  

    • Name: name the application has you wish; as usual use an understandable name, like Hybrid Cloud Print Service
    • Internal URL: this is your internal print server (something like https://serverfqdn/ecp/)
    • Pre authentication method: Passthrough


    • Once the proxy application has been created, edit it to update the App ID URI to http://MicrosoftEnterpriseCloudPrint/CloudPrint


    • Then apply the required permissions by accessing the Required permissions blade to grant Sign in and read user profile permission (if not granted) and then apply by clicking on the Grant permissions


    • Edit the Home page URL to be set as http://MicrosoftEnterpriseCloudPrint/CloudPrint



    Hybrid Cloud Print Service Native Application

    • Create the native application and define the Redirect URI to your on-premises server; which will be something like ms-appx-web://Microsoft.AAD.BrokerPlugin/S-1-15-2-3784861210-599250757-1266852909-3189164077-45880155-1246692841-2835503667


    • Grant the delegated permission for the 2 web applications to access the native application and then click on Grant Permissions


    • Finally add the following URL’s to the Redirect URIs option
      • ms-appx-web://Microsoft.AAD.BrokerPlugin/<NativeClientAppID>



    Registry Update

    This step is important.

    Logon to your print server and edit the URL key located below HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudPrint\MopriaDiscoveryService with the public URL associated with your Discovery application (like https://externalURL/mcs/)

    and then restart IIS (iisreset)



    Configure the MDM policies

    • Access to your Intune portal through the Azure administration portal, access the Device Configuration\Profiles blade and create a new profile


    • Create and deploy a Windows 10 and later profile using the Device Restriction profile type and configure the Cloud Printer options


    • And configure the settings as per below
      • Printer Discovery URL: Internet URL of the discovery end-point (the one ending with the /mcs virtual directory)
      • Printer Access authority URL:<your Azure AD GUID>
      • Azure Native client app ID: The Azure  Native Application ID
      • Print Service URI: http://MicrosoftEnterpriseCloudPrint/CloudPrint
      • Maximum printers to query: any value
      • Printer Discovery Service Resource URI:
      • http://MopriaDiscoveryService/CloudPrint

    • If you want to deploy a Custom profile type, configure the following
    • Add the following OMA-URI
      • Name: CloudPrintOAuthAuthority
      • OMA-URI: ./Vendor/MSFT/Policy/Config/EnterpriseCloudPrint/CloudPrintOAuthAuthority
      • Data type: String
      • Value:<your Azure AD GUID>
      • Name: CloudPrintOAuthClientId
      • OMA-URI: ./Vendor/MSFT/Policy/Config/EnterpriseCloudPrint/CloudPrintOAuthClientId
      • Data type: String
      • Value: The Azure  Native Application ID
      • Name: CloudPrintResourceId
      • OMA-URI: ./Vendor/MSFT/Policy/Config/EnterpriseCloudPrint/CloudPrintResourceId
      • Data type: String
      • Value: http://MicrosoftEnterpriseCloudPrint/CloudPrint
      • Name: CloudPrinterDiscoveryEndPoint
      • OMA-URI: ./Vendor/MSFT/Policy/Config/EnterpriseCloudPrint/CloudPrinterDiscoveryEndPoint
      • Data type: String
      • Value: Internet URL of the discovery end-point (the one ending with the /mcs virtual directory)
      • Name: MopriaDiscoveryResourceId
      • OMA-URI: ./Vendor/MSFT/Policy/Config/EnterpriseCloudPrint/MopriaDiscoveryResourceId
      • Data type: String
      • Value: http://MopriaDiscoveryService/CloudPrint
      • Name: DiscoveryMaxPrinterLimit
      • OMA-URI: ./Vendor/MSFT/Policy/Config/EnterpriseCloudPrint/DiscoveryMaxPrinterLimit
      • Data type: Integer
      • Value: Any value to define the maximum number of printers discovered



    Publish the printer(s)

    There is no easy way (yet) to publish your printers to the Hybrid Print Service.

    To publish your printers, you need to logon with PowerShell to you Azure AD tenant and run the following commands

    IMPORTANT the account you are using to publish the printers needs to be granted read and write permissions on the MopriaDevicedb.db file

    IMPORTANT there will be no options available on Windows 10 clients until a printer is published

    Install the Hybrid Cloud Print PowerShell modules

    • Logon on a Windows 10 Azure AD Joined device
    • Using a PowerShell prompt using the run as administrator

    NOTE you may be prompted to trust the repository

    Find-Module -Name "PublishCloudPrinter"
    Install-Module –Name "PublishCloudPrinter"


    • Use the Publish-CloudPrinter command to publish the printer with the following parameters:
      • Printer: name of the published shared printer – this needs to be the shared printer name
      • Manufacturer: printer manufacturer
      • Model: printer model
      • OrgLocation: a JSON string defining the location of the printer
      • SDDL: string defining the permissions assigned to the printer (to get it run the PowerShell command (Get-Printer “YourSharedPrinterName” -Full).PermissionSDDL). You will have to add O:BA as prefix to the result


      • DiscoveryEndpoint: the external URL of the Discovery Azure Web Application created earlier (the one with /mcs)
      • PrintServerEndpoint: the external URL of the Proxy Azure Web Application created earlier
      • AzureClientID: the application ID of the Azure Native application
      • AzureTenantID: your Azure tenant ID

    The command will then be like this

    Publish-CloudPrinter -Printer "Epson Stylus Office BX620FWD" -Manufacturer "Epson" -Model "Epson Stylus Office BX620FWD" -OrgLocation '{"attrs": [{"category":"country", "vs":"Australia", "depth":0}, {"category":"organization", "vs":"Benoit HAMET", "depth":1}, {"category":"site", "vs":"Sydney,AU", "depth":2}, {"category":"building", "vs":"Home", "depth":3}]}’ -Sddl "O:BAG:SYD:(A;OIIO;GA;;;CO)(A;OIIO;GA;;;AC)(A;;SWRC;;;WD)(A;CIIO;GX;;;WD)(A;;SWRC;;;AC)(A;CIIO;GX;;;AC)(A;;LCSWDTSDRCWDWO;;;BA)(A;OICIIO;GA;;;BA)" -DiscoveryEndpoint "https://<hybrid print service discovery URL>/mcs/" -PrintServerEndpoint "https://<hybrid print service endpoint URL>/ecp/" -AzureClientId "<Azure native app ID>" -AzureTenantGuid "<Azure AD tenant ID>"


    If you are getting the error “Invoke-RestMethod : You don't have permission to Publish.”, check the NTFS permissions assigned on the MopriaDeviceDb.db file



    Using the Hybrid Print Service

    • From a Window 10 Azure AD Joined device, ensure the policies have been sync, then go the Settings\Devices\Printers & Scanners and you should see the option Search for cloud printers



    Hybrid Print Service Management

    The management of the hybrid print service consists either of publishing, querying or removing shared printers.

    Publishing printers has been covered previously.

    Query Hybrid Print Service

    To query the service to gather which printers have been published, use the following command

    The result is a really a crap

    Publish-CloudPrinter –Query -DiscoveryEndpoint “<your discovery endpoint URL – like https://<hybrid print service discovery URL>/mcs/>” -AzureClientId “<your Azure Native App ID>” -AzureTenantGuid "<Azure AD tenant ID>"


    Remove a published printer

    To remove a published printer run the following command

    Publish-CloudPrinter -Unpublish –Printer “<name of the published printer>” -DiscoveryEndpoint “<your discovery endpoint URL – like https://<hybrid print service discovery URL>/mcs/>” –PrintServerEndpoint “<your hybrid print service endoint – like https://<hybrid print service endpoint URL>/ecp/>” -AzureClientId “<your Azure Native App ID>” -AzureTenantGuid "<Azure AD tenant ID>"

    Feb 18
    Azure – New role available in Azure AD for Azure Information Protection management

    A new Directory Role is now available (in preview) to delegate Azure Information Protection management.

    This new role – Information Protection Administrator – allow you the delegation of the AIP management, granting permissions to configure policies labels and settings, configure and manage AIP templates or activate/deactivate AIP functionality.


    As usual you can grant this role from the Azure AD\Users management blade or even better using the Azure AD Privileged Identity Management (PIM)

    Feb 16
    Exchange Online – You can now manage calendar delegation with PowerShell

    The MailboxFolderPermission cmdlet for Exchange Online is getting improved with the adding of a new parameter (SharingPermissionFlags) to let you manage calendar delegation.

    With this parameter, which only applies to Calendar folder when using the Editor access right, you can set the user as a delegate (as you do when using the Delegate Access from Outlook client).

    Below 2 commands using this new parameter:

    • Set the delegate to view private items in the calendar

    Add-MailboxFolderPermission –Identity <delegates mailbox>:\Calendar –User <delegated mailbox> -AccessRights Editor -SharingPermissionFlags Delegate,CanViewPrivateItems

    • Set the delegate to not view private items in the calendar

    Add-MailboxFolderPermission -Identity <delegates mailbox>:\Calendar -User <delegated mailbox> -AccessRights Editor -SharingPermissionFlags Delegate

    1 - 10Next

     ‭(Hidden)‬ Blog Tools


    Benoit is specialized on Microsoft infrastructure (Active Directory, Azure, ForeFront products, Hyper-V, Identity Management, System Center, Windows) and collaboration (BPOS, Exchange, Office 365, SharePoint, Lync/Skype for Business) technologies.

    He has been awarded as Microsoft Most Valuable Professional (MVP) since 2002 - on Windows, then SharePoint and finally Office 365. He has been recoginzed as Microsoft Community Contributor for his work on the Office 365 community in 2013 and 2014.

    He has been involved in early stage of testing phase for many Microsoft products - from Windows to Office 365, including Exchange, SharePoint or Office client and WindowsUpdate.

    He has participated as speaker or Ask The Expert (ATE) at many Microsoft or Quest events. He also participed in writing several books on SharePoint (2003 to 2010).

    With more than 10 years of professional experience, he has a deep knowledge of the Microsoft market and his competitors.


    ​Privacy Information

    This blog is using tracking code for analytics purpose.

    No personal data are stored and maintained.

     Follow me on

     Share This

     Office365 Undercover by Arnaud ALCABEZ

    Retrieving Data


    Microsoft Certified Systems Administrator 
    Microsoft Certified Systems Administrator - Messaging
    Microsoft Certified Systems Engineer 
    Microsoft Technology Specialist 
     Microsoft Certified IT Professional

     Translation Tool

    Translate this page

     FaceBook Fan's Page

     Books I wrote

    Le portail Microsoft SharePoint 
    Microsoft Office SharePoint Portal Server 2003 et WSS au quotidien 
    Microsoft Office SharePoint Server (MOSS) et Office 2007  
    Microsoft Sharepoint 2010