SharePoint Webhooks -- now Generally Available!
Hello everyone, Just wanted to announce that SharePoint Webhooks is now Generally Available. First announced https://dev.office.com/blogs/sharepoint-webhooks-developer-preview-now-available in September, Webhooks https://dev.office.com/blogs/sharepoint-webhooks-is-now-generally-available-build-service-oriented-processes-in-sharepoint. Webhooks are based on industry standard patterns around how services fire notifications that developers can intercept and react to. In particular, within SharePoint we've added support for webhooks against SharePoint list data, including events like Item Added, Updated, and Deleted. A developer could then choose to kick off a process, or programmatically update a document, or fire off a tailored notification to users using information you can get from webhooks. You can find an end-to-end overview and "getting started" with webhooks https://dev.office.com/sharepoint/docs/apis/webhooks/overview-sharepoint-webhooks. Look forward to seeing what you all build with these! -- Mike Ammerlaan, Office Ecosystem Marketing teamIntroducing the SharePoint Migration Tool from Microsoft
Taking advantage of cloud services doesn’t have to be difficult or a long-phased migration project. At Microsoft Ignite we announced a new free, simple, and fast migration solution to help you migrate content from on-premises SharePoint sites and file shares to SharePoint or OneDrive in Office 365. Based on the learning and experience from Microsoft FastTrack, using the SharePoint Migration Tool from Microsoft with a few simple clicks you can begin to bring your information to the cloud and take advantage of the latest collaboration, intelligence, and security solutions with Office 365. Whether you’re looking to migrate from file shares on-premises to SharePoint or OneDrive or from on-premises versions of SharePoint, the SharePoint Migration Tool is designed to support the smallest of migrations to large scale migrations with support for bulk scenarios. Using the SharePoint Migration Tool, you can quickly and easily migrate files from file shares, SharePoint sites, or support bulk migrations with a few simple clicks in the intuitive user interface. The SharePoint Migration Tool also provides detailed information on the process of existing and completed migrations and task reports to help identify and resolve issues that may have occurred during the migration process. For additional details and to see the SharePoint Migration Tool in action, check out the video below. While the SharePoint Migration Tool provides support for many migration scenarios, we recognize your needs may differ in scope and complexity. For more complex migrations, support with adoption and usage, or help planning Microsoft FastTrack includes resources, tools, and experts to make your rollout of Office 365 a success. To learn more about Microsoft FastTrack visit https://fasttrack.microsoft.com/office. In addition, consider one of Microsoft’s many partners that can help ensure your migration to Office 365 is both seamless and successful. Getting Started To get started and preview the new SharePoint Migration Tool from Microsoft visit https://aka.ms/spmt. Resources How to use the SharePoint Migration Tool How the SharePoint Migration Tool works How to format your CSV file for data content migration Create a user mapping file for data content migration SharePoint Online and OneDrive Migration Speed SharePoint Online provided Azure containers and queues for SPO Migration API
New SharePoint /Office Dev Patterns and Practices Webcast - Getting started with SharePoint WebHooks
In this PnP Web Cast we concentrated on showing how to get started with upcoming SharePoint Webhooks. SharePoint Webhooks allow developers to build service integration which subscribe to receive notifications on specific events that occur in SharePoint. When one of those events are triggered, SharePoint will send a HTTP POST payload to subscriber. SharePoint Webhooks will be supported for asynchorinious events, like for ItemAdded or ItemAttachmentAdded. To be able to subscribe to SharePoint Webhooks, you'll need to build a service, which will response on the subscribed validation messages and will process the incoming events. Notice. When this webcast was released SharePoint Webhooks were not yet released. They will be provided for Developer Preview soon with support for list item specific events for lists and libraries. Presentation covers following topics: What are Webhooks? Process for subscribing to a SharePoint Webhook Event notifications from SharePoint Demo setup and details on performed steps Web cast demo shows following details Registration of Azure App used for Webhook Using PostMan to register a Webhook for SharePoint Responding to Webhook validation tokens from ASP.net WebAPI Processing incoming events from SharePoint Using ngrok to develop SharePoint Webhooks locally in your development environment Web cast presenters: Bert Jansen, Vesa Juvonen Presentation used in this web cast is available from http://docs.com/OfficeDevPnP. More guidance and details around the SharePoint webhooks will be soon available from SharePoint developer center. If you have any questions, feedback or comments; please let us know.
SharePoint Site Scripts and Site Designs - April 2018 release
We are happy to announce the availability of additional Site Script Actions for SharePoint Online Site Designs and Site Scripts. These new actions will enable you to further configure automatically the newly created site collections for your employees and will reduce the requirements of having external services integrated with the provisioning process.WDATP API “Hello World” (or using a simple PowerShell script to pull alerts via WDATP APIs)
5 Minutes Low complexity Applying a security solution in an enterprise environment can be a complex endeavor. Customers deploy various layers of protection solutions, investigation platforms and hunting tools. Security Operation teams attempt to tackle this task, but typically lack expensive and experienced human resources to overcome this challenge. Automation is a decent mitigation but automating the security procedures and wiring the security components all together to a solid cyber security solution, requires programmatic access to each solution. In these series of blogs, we will walk you through common automation scenarios that you can achieve with Windows Defender ATP to optimize workflows. For more information on Windows Defender ATP APIs, see the full documentation. We called this blog “Hello World” as every long software journey starts with a simple step. We’ll show you how to programmatically extract Windows Defender ATP alerts with a PowerShell script. You can schedule this script to run on any machine and you may modify it to use the alert information in your specific use case. We can imagine a handful of standard use cases where a Security Operations Center (SOC) can leverage this basic capability. Some scenarios where this can be applied include use with security information and event management (SIEM) connectors, ticketing systems, and security orchestration and response (SOAR) solutions. SIEM connectors may be the simplest example while ticketing systems are a common one, and SOAR solutions may be a complex use case. So let gets started…. How long it takes to go through this example? It only takes 5 minutes done in two steps: Application registration: takes 2 minutes Use examples: only requires copy/paste of a short PowerShell script Do I need permission to connect? For the app registration stage, you must have a Global administrator role in your Azure Active Directory (Azure AD) tenant. Step 1 - Register the app in Azure Active Directory With your Global administrator credentials, login to the Azure portal. Azure Active Directory > App registrations > New registration. In the registration form: Name - Name your application. Supported account type – leave the default setting. Redirect Uri – leave empty. Click Register The application I created is the authentication entity, just like a service account. I now need to set permissions to my app and save its credential for later use. On your new application page, click API Permissions > Add permission > APIs my organization uses > type WindowsDefenderATP and click on WindowsDefenderATP Note: WindowsDefenderATP does not appear in the original list. You need to start writing its name in the text box to see it appear Choose Application permissions > Alert.Read.All > Click on Add permissions: After clicking the Add Permissions button, on the next screen we need to grant consent for the permission to take effect. Press the "Grant admin consent for {your tenant name}" button. As explained, the registered app is an authentication entity with permission to access all alerts for reading. Now I need to get and store the authentication and authorization credentials: Key (application secret), Application ID, and Tenant ID Think of your secret like a password, Application ID as username and Tenant ID as a domain. To get credentials: In your application page, Click Certificate & Secrets Specify a key description and set an expiration for 1 year. Click Add. The application key will appear. IMPORTANT: Copy and store this key in a safe place. Treat it like a password. Get your application ID and your tenant ID: On your application page, go to Overview and copy the following Done! You have successfully registered an application. You may reuse this application when going through the exercises that we’ll be using in future blogs and experiments. Now we’ll need to connect the API which means getting a token. The token is proof for Windows Defender ATP that an API call is authenticated and authorized. Connecting the API: Copy the text below to PowerShell ISE or to a text editor. # That code get the App Context Token and save it to file name "Latest-token.txt" under the current directory # Paste below your Tenant ID, App ID and App Secret (App key). $tenantId = 'f839b112-d9d7-94d27-9bf6-94542403f21c' ### Paste your own tenant ID here $appId = '94fbf312-ae3f-47f4-8eeb-d375d1299e8f' ### Paste your own app ID here $appSecret = 'ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890=' ### Paste your own app keys here $resourceAppIdUri = 'https://api.securitycenter.windows.com' $oAuthUri = "https://login.windows.net/$TenantId/oauth2/token" $authBody = [Ordered] @{ resource = "$resourceAppIdUri" client_id = "$appId" client_secret = "$appSecret" grant_type = 'client_credentials' } $authResponse = Invoke-RestMethod -Method Post -Uri $oAuthUri -Body $authBody -ErrorAction Stop $token = $authResponse.access_token Out-File -FilePath "./Latest-token.txt" -InputObject $token return $token Save the script to file. You can name it "Get-Token.ps1". Running this script by pressing F5 will get a token and save it in the working folder under the name "./Latest-token.txt". Note: If you are getting an error: \Get-Token.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170. That error indicates that your Powershell execution policy not allowing you to run scripts. You can change the execution policy by running that command in Powershell console: PS c:\>>Set-ExecutionPolicy unrestricted -Scope CurrentUser Consider consulting with your system administrator about your organization’s Powershell execution policy. Sanity Check In your browser go to: https://jwt.ms/ Copy the token (the content of the Latest-token.txt file). Paste in the top box. Look for the "roles" section. Find the Alert.Read.All role. Now let’s gets the alerts, Copy the following text to a new PowerShell Script. # Returns Alerts created in the past 48 hours. $token = ./Get-Token.ps1 #run the script Get-Token.ps1 - make sure you are running this script from the same folder of Get-Token.ps1 # Get Alert from the last 48 hours. Make sure you have alerts in that time frame. $dateTime = (Get-Date).ToUniversalTime().AddHours(-48).ToString("o") # The URL contains the type of query and the time filter we create above # Read more about other query options and filters here $url = "https://api.securitycenter.windows.com/api/alerts?`$filter=alertCreationTime ge $dateTime" # Set the WebRequest headers $headers = @{ 'Content-Type' = 'application/json' Accept = 'application/json' Authorization = "Bearer $token" } # Send the webrequest and get the results. $response = Invoke-WebRequest -Method Get -Uri $url -Headers $headers -ErrorAction Stop #Extract the alerts from the results. $alerts = ($response | ConvertFrom-Json).value | ConvertTo-Json #Get string with the execution time. We concatenate that string to the output file to avoid overwrite the file $dateTimeForFileName = Get-Date -Format o | foreach {$_ -replace ":", "."} #save the result as json and as csv $outputJsonPath = "./Latest Alerts $dateTimeForFileName.json" $outputCsvPath = "./Latest Alerts $dateTimeForFileName.csv" Out-File -FilePath $outputJsonPath -InputObject $alerts ($alerts | ConvertFrom-Json) | Export-CSV $outputCsvPath -NoTypeInformation Save the file in the same folder you saved the previous script (Get-Token.ps1). You can run the script by right-clicking on the file and choosing "Run with PowerShell" or run it from PowerShell console. NOTE: If you are using powershell_ise.exe make sure to change directory to the directory with the scripts. You will now see two files (json and csv) created in the same folder as the scripts. The files are the latest alert from your tenant in the past 48 hours. You’re all done! You have just successfully: Created and registered and application Granted permission for that application to read alerts Connected the API Use a PowerShell script to return alerts created in the past 48 hours In the next blog, we’ll walk you through updating alert status programmatically. I invite you to suggest more use cases that you’d like for us to blog about, provide feedback, and ask questions about this post! Thanks! Haim Goldshtein, security software engineer, WDATP Dan Michelson, program manager, WDATP @Ben Alfasi, software engineer, Windows Defender ATPNew SharePoint PnP webcast - Using external JS libraries from client-side web part
New PnP webcast concentrated on the options and considerations around using external JavaScipt libraries within your SharePoint Framework client-side web part. Check following blog post from dev.office.com/blogs for more details. SharePoint PnP Webcast – Referencing external JavaScript libraries from client-side web part If you have any comments, feedback or other thoughts, just let us know.SharePoint / Office 365 Dev Patterns and Practices - September 2016 release
We are happy to announce availability of PnP September 2016 release. You can find all release details from the following blog post under dev.office.com SharePoint / Office 365 Dev Patterns and Practices - September 2016 Release You can also join our monthly community call for live demos on key new capabilities. September monhtly community call is on 13th of September at 8 AM PDT - You can download invite from http://aka.ms/SPPnP-Call. Agenda for the Tuesday 13th of September community call at 8 AM PDT / 5 PM CET: Summary on the September 2016 release and other program updates - Vesa Juvonen ~20-25 min What's new in PnP Partner Pack v2.0 - Paolo Pialorsi (Piasys.com) ~10-15 min Demo on new PnP Starter Intranet for SharePoint Online solution - Franck Cornu (CGI) ~10-15 min Demo on new SharePoint.React.SupportTicket sample - Brian Michely (Microsoft) ~10-15 min
