The home site app for Microsoft Teams

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

This week at Microsoft Ignite we announced the new home site app. The app gives employees a gateway to your organization, starting with the app’s name and icon, which you can customize to reflect the identity of your organization or your intranet. The app’s multi-level navigation lets people find sites across the organization, including portals, teams, communities and applications.

 

We are happy to see the excitement for this in the community and with our customers. Many of you have asked for additional information. As part of Ignite we have released a new session, on demand, focused on the home site app.

 

We have also put together an FAQ with the most common questions we have been asked.

 

Home site app

Q: Can any site be pinned as a Home site app in Teams? 

A: Communication sites designated as Home Sites are eligible for pinning in Teams as the Home site app using our default configuration flow. 

 

Q: Where are global navigation links curated? 

A: Links for global navigation are managed through the home site, by home site owners, freeing global admins from having to play the role of curator 

 

Q: Can my classic site be pinned in Teams ? 

A: Only home sites are eligible to be pinned as the home site app in Teams with our default configuration flow.  Home sites must be modern SharePoint communication sites. 

 

Q: What is difference between Home site app and Home page pinned as tab? 

A: The home site app provides organizations to pin company branded entry point to their intranet as a top level app in Teams.  It provides an immersive site consumption experience, complete with navigation, mega-manus and support for tenant wide search.  It also provides quick access to company curated resources, important sites and news similar to those provided by the SharePoint App Bar in the web.  Home pages (or any other SharePoint pages) pinned as tabs in Channels provide ways to bring content directly into Team collaboration scenarios, and these pages have navigation and search elements removed to facilitate focus on the page content itself. 

 

Q: Do I need a Home site app for the Global nav to show up in Teams? 

A: Yes, the global navigation links are stored in the home site of a tenant, and is required in order for the navigation panel to appear in the home site app in Teams 

 

Q: Can a Team site be a Home site? 

A: No. Only communication sites can be made a Home site in a tenant. 

 

We are humbled and honored by the reaction to this upcoming feature and appreciate all the engagement with us. Please, keep your feedback and questions coming.

The above is kindly provided by the Microsoft Tech Community!

SharePoint admin and migration announcements at Ignite 2020

SharePoint admin and migration announcements at Ignite 2020

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

We are on a journey to align the SharePoint admin center with the Microsoft 365 suite designing it to be more interconnected and aligned with the changing collaboration needs of your people. Today at Microsoft Ignite 2020, we announced several new updates to the overall SharePoint admin center experience – to enable visual, actionable management of your intelligent intranet, report on what content services power your content productivity and ease of migration from Box:

 

  • Meet the updated SharePoint admin center home page with actionable insights
  • Improved visibility on where sites are created from and by whom
  • Microsoft 365 migration for Box
  • Bringing OneDrive settings into the SharePoint admin center

 

Active sites in the SharePoint admin center now showcase where the site was created from, by whom and whether it is yet connected to Microsoft Teams.Active sites in the SharePoint admin center now showcase where the site was created from, by whom and whether it is yet connected to Microsoft Teams.

The intelligent intranet is personal, collaborative, and ever changing. The updates highlighted below will be coming to your Microsoft 365 tenant by the end of this calendar year (2020) – all to monitor and manage the state of your organization’s intranet and utilize the new experiences to stay productive – especially when you have 100s or 1000s of sites to manage, across terabytes or petabytes of active content.

 

Meet the updated SharePoint admin center home page with actionable insights

Everything we build is inspired from the feedback we receive from the community and is designed to make your day-to-day administration easier. One of the most common pieces of feedback we receive is around insights and reporting, right behind admin experience consistency throughout the suite. So, we’re working on loading up the default SharePoint admin center home page with all the information, insights and contextual actions you need at a glance – and hey, it looks a lot like what you’ve seen as updates to the Microsoft 365 admin center.

 

1 of 4 - the new SharePoint admin home page showing several cards: Site search, Active users, and Service health.1 of 4 – the new SharePoint admin home page showing several cards: Site search, Active users, and Service health.

Beyond the default set of cards, you can create customizable search cards. Simply navigate to the Active sites page, create a view with the desired columns and settings intact and then click the Track button. This puts a new custom card on the home page that you can place in any location of the home page layout.

 

3 of 4 – as you scroll the new SharePoint admin home page further, you see more cards: Sensitivity labels across sites, OneDrive usage, and OneDrive file activity.3 of 4 – as you scroll the new SharePoint admin home page further, you see more cards: Sensitivity labels across sites, OneDrive usage, and OneDrive file activity.

We, too, are adding proactive recommendations to the top of the home page. These recommendations are tailored to each individual and helps you learn about improvements that you may not know about.

 

4 of 4 – as you scroll back to the top of the new SharePoint admin home page, at time you’ll see proactive recommendations – like above suggesting you modernize your root site (including more information and quick-start button).4 of 4 – as you scroll back to the top of the new SharePoint admin home page, at time you’ll see proactive recommendations – like above suggesting you modernize your root site (including more information and quick-start button).

You can create your preferred home page experience using any combination of the following visual, actionable cards:

 

·         Site search

·         Message center

·         Service health

·         Active users

·         SharePoint site usage

·         SharePoint file activity

·         SharePoint storage usage

·         Sites creation breakdown

·         OneDrive usage

·         OneDrive file activity

·         Term store operations

·         Sensitivity labels across sites

… plus, the ability to create your own custom search-driven cards as described above.

 

Create your own custom search-driven cards; above shows pivot of sites on certain criteria (left) and the card that gets created on the home page (right) after clicking the track button.Create your own custom search-driven cards; above shows pivot of sites on certain criteria (left) and the card that gets created on the home page (right) after clicking the track button.

Last, anyone who is assigned as a SharePoint admin within your organization can personalize their own home page experience. Thus, each SharePoint admin can focus on their main tasks, especially when they differ across administration delegation.

 

SharePoint admin center – updated home page dashboard | Roadmap ID: 68812.

 

Improved visibility on where sites are created from and by whom

The mystery of who created a site and from where has mystified SharePoint seekers for ages. Seek no more. The origins that cast lore about the land stops soon.

 

The Active sites tab is getting new insights. At a glance, you’ll be able to tell where a site was created from – like via PowerShell, API or Microsoft Teams – and in a column nearby, you’ll be able to see who the site was created by.

 

Use the Created from column to filter a list of sites down by where it was created from.Use the Created from column to filter a list of sites down by where it was created from.

Microsoft Teams is an important productivity integration for your people and their content – powered by SharePoint. So, to improve visibility on which sites are already connected to Teams, you’ll find a new column that tells you exactly that – whether the site is yet connected to Teams, or not. And if it isn’t, the ability to ‘Teamify’ the site is merely one-click away.

 

Easily see if a SharePoint team site has an existing connection to Microsoft Teams.Easily see if a SharePoint team site has an existing connection to Microsoft Teams.

SharePoint admin center – site creation source | Roadmap ID: 68813.

 

Microsoft 365 migration for Box

With our recent Mover acquisition, we are excited to expand our capabilities to allow moving content from third-party cloud storage providers directly from within the SharePoint admin center – starting with Box.com migration.

 

Scan discovery (you’ll see files and folder and quantity), assessment, and then move to migrate (where you’ll see source and progress).Scan discovery (you’ll see files and folder and quantity), assessment, and then move to migrate (where you’ll see source and progress).

You’re in control every step of the way, and we’re there to help. As you connect to a Box enterprise account, the service begins discovering users and their files. We auto-map to individual’s OneDrive accounts. You, too, can manually map the destination to specific OneDrive user accounts, SharePoint sites, or Teams Files (a SharePoint document library under the covers).

 

Start your Box migration from within the SharePoint admin center Migration tab in Microsoft 365.Start your Box migration from within the SharePoint admin center Migration tab in Microsoft 365.

The rest is a seamless transition of your files and folders to Microsoft 365 – including the transfer and conversion of Box notes to Word documents.

 

Try this later in the year. Our plan is to move more of the Mover capabilities into the SharePoint admin center in Microsoft 365.

 

SharePoint admin center – Migration Manager: Box migrations | Roadmap ID: [68816].

 

Bringing OneDrive settings into the SharePoint admin center

Less admin is more. Especially when the less means better managing the same platform across various experiences. In this case, we want to make it easier to access OneDrive settings from within your SharePoint admin center – without needing to go to the OneDrive admin center.

 

Access many OneDrive settings from within the SharePoint admin center Settings page.Access many OneDrive settings from within the SharePoint admin center Settings page.

Go to the Settings tab and find ease-of-access to manage default storage limits, allows notifications, set default retention owners for deleted users and manage important sync settings (including sync reporting  (announced at Ignite 2020 and coming soon).

 

And as mentioned above, you can use two new OneDrive-specific home page cards to see OneDrive usage and OneDrive file activity.

 

SharePoint admin center – OneDrive settings | Roadmap ID: 68814.

 

Additional resources

Monitor and manage SharePoint investments in Microsoft 365” presented by Dave Minasyan, Rk Menon, and Trent Green:

 

What’s new to easily migrate your content to Microsoft 365” presented by Eric Warnke and Yogesh Ratnaparkhi:

 

Closing

Managing SharePoint and OneDrive in Microsoft 365 continues to improve. Beyond new innovation, take a moment to learn more about the SharePoint admin role in Microsoft 365 to best manage sites, control external sharing, move content into Microsoft 365, manage metadata, and more.

 

We invite you to engage our FastTrack team to help with adoption and migration. Our goal is to empower you and every person on your team to achieve more. Let us know what you need next. We are always open to feedback via UserVoice and continued dialog in the SharePoint community in the Microsoft Tech Community —and we always have an eye on tweets to @SharePoint. Let us know.

 

Thanks, Mark Kashman – senior product manager – Microsoft 365

The above is kindly provided by the Microsoft Tech Community!

Innovations for workplace communications and employee engagement in Microsoft 365

Innovations for workplace communications and employee engagement in Microsoft 365

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

In an increasingly volatile world, organizational resilience depends upon the agility and responsiveness of your people. It’s more critical than ever to connect, inspire, and activate people. But it is also more difficult than ever. While many people may have adapted to working remotely, we hear from customers that it’s challenging to connect people, particularly outside of their core working groups, to drive culture and communication, and foster knowledge sharing and innovation.

Today, at Microsoft Ignite, we announced innovations that transform workplace communications, and empower communicators with integrated storytelling tools to inform, engage and inspire people across the organization. These innovations are informed by you, our customers. Top announcements include:

 

  • Home site app for Microsoft Teams. Bring your home site and the best of your intranet directly into Microsoft Teams—seamlessly. The home site app gives your users global navigation across sites, communities, and teams; quick access to sites they use regularly; and a personalized news feed.
  • SharePoint app bar. Create a consistent navigation experience to every site on your intelligent intranet, featuring quick access to important sites across the organization, personally relevant sites, and the news feed.
  • Boost news in SharePoint. Prioritize important news and announcements to appear at the top of news feeds across Microsoft 365. You can boost the visibility of a news article for a set time, until an employee has seen your content, or until a viewer has seen the item in their feed a set number of times.
  • Share news to email, Microsoft Teams, and Yammer. Share a news article directly to your audience’s team, community, or inboxes.
  • Enhancements for communicators in Yammer. Send notifications for priority announcements to the inboxes of all community members or raise the visibility of a post by featuring it in the community and discovery feed. And, with delegate posting, designated users can share messages and announcements to the organization on leadership’s behalf.
  • Built-in templates. Quickly deploy robust scenarios by using predefined sites that integrate the superpowers of Microsoft 365. Easily customize built-in templates to your needs, such as the template for Leadership Connection, and apply them to any existing SharePoint site to give it new superpowers and a beautiful design.
  • Insights for communicators. Understand your reach, impact, and engagement across Microsoft 365 by using new analytics in SharePoint, such as dwell time on content, heatmap views of interaction, and automatic analytics digest powered by AI. Combined these insights with analytics in Yammer, such as enhanced Community Insights, Live Events, and Question and Answers.

The intelligent intranet and Teams: better together

For many of you, the intranet is a canvas for communications, and for nearly two decades, SharePoint has been the leading platform for intranets, enabling organizations to connect the workplace, share information, and deliver rich employee experiences. Recent innovations in SharePoint like home sites, multilingual support, and audience targeting allow customers to create award-winning intranets in Microsoft 365, with no code.

As more people use Teams as a hub for teamwork, customers have asked us to integrate the superpowers of SharePoint with Teams, to reach people effectively where they work.

Today, we’re pleased to announce the new home site app for Teams, which brings your home site and the best of your intelligent intranet to Teams. The app gives users a gateway to your organization, starting with the app’s name and icon, which you can customize to reflect the identity of your organization or your intranet. The app’s multi-level navigation lets people find sites across the organization, including portals, teams, communities and applications.

Sites built on modern SharePoint will render inside Teams itself. And the app makes it easy to share and discuss content from intranet sites in Teams channels and chat.

 

SharePoint Landing.png

 

With the home site app, people can tap into news and resources across the intelligent intranet without leaving the hub for teamwork. And communicators can build and deliver rich communications experiences in Teams.

 

Global navigation and news, on any site

Customers have also asked us to provide a global navigation experience that connects the workplace. The new SharePoint app bar brings a consistent navigation experience to every site on your intelligent intranet, featuring quick access to important sites across the organization, personally relevant sites, and the news feed. The customizable, global navigation in the app bar is shared with the home site app, giving employees that consistent navigation experience across Teams and the browser.

 

globalNav_news.png

 

Improvements to news feeds and digests

Communicators told us that it’s harder than ever to get the right information to the right people, at the right time, across applications and devices. Today we announced improvements to news feeds and news digests.

 

The news feed delivers an intelligent view of news, targeted to you based on factors like your role or location, and further personalized based on signals in Microsoft Graph about where, how, and with whom you work. But communicators have told us that not all announcements and news are equal. Sometimes you need to boost the visibility of important news articles in the feed, rather than relying solely on AI. Soon, you can boost a news post until it has been read, for a set number of impressions, or until a given date. When the criteria is satisfied, the post returns to its normal position in the feed.

 

NewsBoost_Config.png

 

We’re delivering an enhanced news feed that supports boosting news in Edge, in news web parts, and in the SharePoint start page. In the future, we’ll be bringing this improved news feed to other experiences, and we’ll be adding new superpowers to the feed.

 

News Boost - Edge.png

And employees have told us that keeping up with so much news and information can be challenging. To help you keep up-to-date with workplace communications, the automatically generated news digest will send an email summary, curated by AI, of news articles you may have missed or not read that week. The digest will help ensure people stay on top of news that you have boosted. And you can customize the news digest with your organization’s branding.

 

newsBoost_email.png

For communities in Yammer, we’ve recently empowered community managers to pin conversations to the top of the feed, and now you can feature a conversation, which showcases the conversation in the community feed and raises its visibility in Yammer’s home feed. You can also post priority announcements, which raises the visibility of notifications in community members’ inboxes. Additionally, leaders can delegate the ability to post to Yammer to their communications leads, allowing communicators to post news and announcements on behalf of leaders.

 

Reach and engage people in the apps they use every day

Communicators have also told us that to engage an audience that represents diverse generations and workstyles, you need to reach people where they are. You can share news and announcements to people and engage them across your SharePoint intranet, and now, Teams and Yammer.

 

You can share a news article to a Teams channel or a Yammer community, to reach your audience and encourage conversation about the item. You can spark richer engagement with the superpowers of these apps. For example, when sharing a news article to Yammer, you can add a poll to measure sentiment, or share it as a question to crowdsource ideas.

 

Yammer-sharetoTeams.png

 

Create captivating communications experiences

Customers have told us that they do not want to spend precious resources and brain cycles designing intranet sites. Last year we introduced the lookbook to help you build beautiful employee experiences. 

 

Now you can use built-in templates to give any existing site an extreme makeover. Templates, like the leadership connection template, have been purpose-built to support specific scenarios. They integrate the superpowers of SharePoint and other Microsoft 365 experiences, and deliver a beautiful, out-of-box design that you can customize with no code to reflect your branding and your needs. Of course, templates are responsive and accessible, so your experiences can be inclusive of all users, across devices.

 

Yammer_builtintemplates.png

 

Today we also announced that SharePoint spaces reaches general availability this fall. SharePoint spaces enable anyone to create immersive and engaging mixed reality experiences that showcase 3D content, models and 360° imagery, and bring 2D content to life in stunning new ways. Spaces transform scenarios from hosting virtual events to onboarding employees, and can be experienced across devices, with a browser or a headset.  The SharePoint spaces team sends a special “Thank you!” to our numerous early adopters and preview customers who provided us with rich feedback to guide the development of this revolutionary experience.

 

 

Foster a tighter workplace community

Because customers emphasize the need to connect and engage everyone, across the organization, we continue to invest in communities that foster a culture of inclusion, where everyone feels empowered to contribute to the conversation. 

 

Innovations for Yammer’s All Company community turn it into a powerful tool for informing and engaging the entire organization, from the top-floor to the shop floor. Posts to the All Company community are discoverable by everyone, and anyone can engage. Now, you can customize the All Company community with your organization’s branding, and you can restrict who can post announcements or start new conversations in the community.

 

Yammer-AllCompanyCommunity.png

 

And when you share an announcement in Yammer’s All Company community, notifications are generated for everyone in the organization across Yammer, Outlook, and now Teams; across web, desktop and mobile. People can engage from the apps they use every day and express themselves with nuance using new reactions.

 

Reactions mobile.gif

 

Better measure the impact of your communications

Finally, communicators have emphasized the importance of measuring the reach and effectiveness of communications. New insights include a heatmap of interaction or dwell time on content.  An analytics digest, powered by AI, will automatically be sent to the author of a news post one week after content is posted, and provides suggestions to increase visibility of their post. And in Yammer, updated Community Insights empower communicators and community managers with detailed analytics for Conversations, Live Events, and Question and Answers.

 

Community Insights.png

 

It has never been more critical for organizations to connect, inspire, and activate their employees.  Microsoft 365 brings you innovations that transform workplace communications. Whether you’re a leader, an HR or communications professional, or a communicator anywhere in the organization, we will continue to invest in integrated storytelling capabilities that empower you to inform, engage and inspire people, and to measure and improve your impact. We look forward to your feedback on these innovations, and to sharing the journey ahead.

 

The above is kindly provided by the Microsoft Tech Community!

Microsoft 365 & SharePoint Community (PnP) – September 2020 update

Microsoft 365 & SharePoint Community (PnP) – September 2020 update

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

september-pnp-promo.jpg

 

Microsoft 365 & SharePoint Ecosystem (PnP) September 2020 update is out with a summary of the latest guidance, samples, and solutions from Microsoft or from the community for the community. This article is a summary of all the different areas and topics around the community work we do around Microsoft 365 and SharePoint ecosystem during the past month.

 

Thank you for being part of this initiative. Sharing is caring!

 

 

Got feedback, suggestions or ideas? – don’t hesitate to contact.

The above is kindly provided by the Microsoft Tech Community!

Microsoft 365 & SharePoint PnP Weekly – Episode 94

Microsoft 365 & SharePoint PnP Weekly – Episode 94

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

pnp-weekly-episode-95-promo.jpg

In this weekly discussion of latest news and topics around Microsoft 365, hosts – Vesa Juvonen (Microsoft), Waldek Mastykarz (Rencore), are joined by Tomasz Poszytek, an independent consultant and MVP from Poland.

 

They talk about Thomasz’s background and how we crew to be an independent consultant running his own business. Key tips from him for anyone who might be looking into doing the same. Discussions on the business automation and the different tools which we have had around these processes in past. Touching the challenge of the licensing models from Microsoft and how that has been simplified from the past… but could be further simplified in future.

 

Thomasz also talks about this experiences on being a project manager and how he decided to rather be a consultant. In this episode, 21 recently released articles from Microsoft and the PnP Community are highlighted.

 

This episode was recorded on Monday, September 7, 2020.

 


Did we miss your article? Please use #PnPWeekly hashtag in the Twitter for letting us know the content which you have created. 

 

As always, if you need help on an issue, want to share a discovery, or just want to say: “Job well done”, please reach out to Vesa, to Waldek or to your PnP Community.

 

Sharing is caring!

The above is kindly provided by the Microsoft Tech Community!

Microsoft 365 & SharePoint PnP Weekly – Episode 94

Microsoft 365 & SharePoint PnP Weekly – Episode 94

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

pnp-weekly-episode-94-promo.jpg

 

In this weekly discussion of latest news and topics around Microsoft 365, hosts – Vesa Juvonen (Microsoft), Waldek Mastykarz (Rencore), are joined by. by Phil Worrell (Swisscom) –  Community Evangelist based in Switzerland.   

 

The trio discusses the significance of the datacenter and cloud adoption in Switzerland, embracing the new work reality, and REgarding 365 – a WW community of MVPs delivering opinions, interviews, conferences, blog posts, weekly talk show and support on everything Microsoft 365.   

 

Waldek and the PnP CLI team are gearing up to ship v3.0 of PnP CLI for Microsoft 365 this weekend. In this episode, 17 recently released articles from Microsoft and the PnP Community are highlighted.

 

This episode was recorded on Monday, August 31, 2020.

 


Did we miss your article? Please use #PnPWeekly hashtag in the Twitter for letting us know the content which you have created. 

 

As always, if you need help on an issue, want to share a discovery, or just want to say: “Job well done”, please reach out to Vesa, to Waldek or to your PnP Community.

 

Sharing is caring!

The above is kindly provided by the Microsoft Tech Community!

TLS 1.0 and 1.1 deprecation

TLS 1.0 and 1.1 deprecation

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

In the dazzling array of services among the Microsoft cloud offerings, the rollout of TLS 1.0/1.1 deprecations is not being done all at once. This has lead to some confusion and questions around which endpoints are dropping the older TLS support and when.

 

Here I want to provide some dates and times of the endpoints, along with some .NET code guidance on how to use the newer TLS protocol (1.2), with some more information on TLS across the Microsoft Cloud.

 

So to begin, here are some of the endpoints that we know of. 

Service end date Release
Office 365 (Exchange/SharePoint/etc)    
Office 365 Dod/GCC 1/1/2020  
Office 365 consumer 10/15/2020  
Graph    
Graph Government 8/5/2020  
Graph Consumer 10/15/2020  
Azure    
Azure Guest OS images 1/1/2019 Family 6 release
Azure Application Proxy 1/31/2019  
Azure intra-service traffic 1/1/2020  
Azure SQL DB managed instance (pre SQL 2016) 1/1/2020  
Azure Cosmos DB  7/29/2020  
Azure File Sync 8/1/2020  
Azure AD registration service in all sovereign clouds (GCC High, DoD etc.) 8/31/2020  
Azure Automation 9/1/2020  
Azure AD registration service in all commercial clouds 10/30/2020  
Azure App Services (Web apps/functions/etc.) no announced timeline, can be set by admin still. ??  

 

If you are not sure about a particular endpoint, you can use this powershell to test the endpoint to see which versions of TLS it supports-

 

 

<#
Created by: whall
Date Created: 3/25/2020

Product Area Tags: Connectivity

Technology Tags: SSL TLS

Use Case:
Shows which version(s) of TLS is supported for a URL

Description:
When you run this, it checks each TLS type connection to see if it is supported.

Parameters:
-url this is the URL of the site you are testing against

Keywords: sockets secure https

Code Example Disclaimer:
Sample Code is provided for the purpose of illustration only and is not intended to be used in a production environment. THIS SAMPLE CODE AND ANY RELATED INFORMATION ARE PROVIDED ‘AS IS’
-This is intended as a sample of how code might be written for a similar purpose and you will need to make changes to fit to your requirements.
-This code has not been tested.  This code is also not to be considered best practices or prescriptive guidance. 
-No debugging or error handling has been implemented.
-It is highly recommended that you FULLY understand what this code is doing  and use this code at your own risk.

#>

#TLS check
param([Parameter(Mandatory=$true)][string]$url)

function TLSAvailable([string]$url){

Write-Host =======================
Write-Host $url
Write-Host =======================

[System.Net.ServicePointManager]::SecurityProtocol = “Tls”

try{
$resp1 = Invoke-WebRequest -uri $url -Method GET -DisableKeepAlive
if($resp1.StatusCode -eq 200){
Write-Host “TLS/SSL 1.0 supported” -ForegroundColor green
}
}catch {
Write-Host “TLS/SSL 1.0 not supported” -ForegroundColor Red
#$_.Exception
}

[System.Net.ServicePointManager]::SecurityProtocol = “Tls11”
try{
$resp2 = Invoke-WebRequest -uri $url -Method GET -DisableKeepAlive
if($resp2.StatusCode -eq 200){
Write-Host “TLS/SSL 1.1 supported” -ForegroundColor green
}
}catch {
Write-Host “TLS/SSL 1.1 not supported” -ForegroundColor Red
#$_.Exception
}

[System.Net.ServicePointManager]::SecurityProtocol = “Tls12”

try{
$resp3 = Invoke-WebRequest -uri $url -Method GET -DisableKeepAlive
if($resp3.StatusCode -eq 200){
Write-Host “TLS/SSL 1.2 supported” -ForegroundColor green
}
}catch{
Write-Host “TLS/SSL 1.2 not supported” -ForegroundColor Red
#$_.Exception
}
Write-Host =======================

}

TLSAvailable -url $url

 

 

 

Azure Web Application Services

If you are running a .NET web application in the Azure web application services, you can set the TLS level under the application settings as below-

 
 

Annotation 2020-08-28 133047.png

  

.NET Framework Code

If you are compiling your code for .NET framework 4.7 (4.7.1 for WCF apps) or later, it will use the default TLS version for the OS.

 

If you complied to a previous .NET framework version, it will use older versions of TLS unless you apply the right patch, and use one of the following methods-

  1. Set a registry setting to force all .NET code to use strong cryptography
  2. Set a config setting for the app context overrides to use the strong cryptography
  3. Add a line of code to change the TLS version used for HTTPS calls

 

Method 1 (System wide registry change)-

This enables something called strong cryptography which makes .NET use the strongest cryptography available currently. This affects all .NET applications with one registry change (per CLR version).

Enable strong cryptography for .NET CLR 4 versions (64 bit)-

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkv4.0.30319]

“SchUseStrongCrypto”=dword:00000001

[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkv4.0.30319]

“SchUseStrongCrypto”=dword:00000001

 

Enable strong cryptography for .NET CLR 2 versions (64 bit)-

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkv2.0.50727]

“SchUseStrongCrypto”=dword:00000001

[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkv2.0.50727]

“SchUseStrongCrypto”=dword:00000001

 

 

Method 2 (Config file change)-

Add the following to your .NET config file

<runtime>

<AppContextSwitchOverrides value=”Switch.System.Net.DontEnableSchUseStrongCrypto=false” />

</runtime>

 

Method 3 (Hardcoded in the application)-

Use this line of C# code in your application during the initialization so that all web calls will use the newer TLS 1.2 protocol-

 

System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

 

 

If you are using PowerShell you can use the same object with this-

 

[System.Net.ServicePointManager]::SecurityProtocol = “Tls12”

 

 

More on these here-

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls

 

Browser Support (Edge/Chrome/Edge legacy/IE/Firefox/Safari)

The following clients are known to be unable to use TLS 1.2. Update these clients to ensure uninterrupted access to the service.

 

  • Android 4.3 and earlier versions
  • Firefox version 5.0 and earlier versions
  • Internet Explorer 8-10 on Windows 7 and earlier versions
  • Internet Explorer 10 on Windows Phone 8
  • Safari 6.0.4/OS X10.8.4 and earlier versions

 

Edge chromium disabled 1.0 and 1.1 around July 2020 (ver 84).

For all supported versions of Internet Explorer 11 and Microsoft Edge Legacy (EdgeHTML-based), TLS 1.0 and TLS 1.1 will be disabled by default as of September 8, 2020.

 

TLS 1.3

The next version of TLS is already implemented in some browsers, and is just around that corner, but as of yet should not be causing issues since TLS 1.2 is just getting to the lowest mandatory version.

 

More information

For more information on the patches for various products and more details to some of the .NET settings related to TLS please see the following articles.

 

Azure

https://azure.microsoft.com/en-us/updates/azuretls12/

https://azure.microsoft.com/en-us/updates/?query=TLS

 

Windows/.NET/SQL/SharePoint (on-Prem)

SQL-

https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server

 

SharePoint (this covers .NET/windows/SQL/browsers as well)-

https://docs.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2019

 

.NET 4.5-

https://docs.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2019#34—enable-strong-cryptography-in-net-framework-45-or-higher

 

.NET 3.5 update for TLS 1.1/1.2 support-

https://docs.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2019#35—install-net-framework-35-update-for-tls-11-and-tls-12-support

 

.NET programming guidance-

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls

 

The above is kindly provided by the Microsoft Tech Community!

OOB Approval workflows are missing on SharePoint online site

OOB Approval workflows are missing on SharePoint online site

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

SharePoint OOB Approval workflows are missing on SharePoint online site even after activatingreactivating the “Workflows” site collection feature.

 

Missing workflow templates: 

Publishing Approval

Approval – SharePoint 2010 

Collect feedback – SharePoint 2010

Collect Signatures – SharePoint 2010

 

Issue:

SharePoint OOB Approval workflows are missing on SharePoint online site even after activatingreactivating the “Workflows” site collection feature.

 

We just see below templates,

image.png

And in SharePoint designer, Wfpub contents are shown as folder and NOT as a library.

image.png

 

Background:

  • Workflows feature depends on OffWfCommon (c9c9515d-e4e2-4001-9050-74f980f93160). 
  • OffWfCommon generates wfpub library when activated.
  • Workflows features will deploy globally reusable workflows in wfpub when activated.
Initially activating Workflows means activating OffWfCommon and Workflows at the same time.
So, OffWfCommon will generate wfpub library and Workflows will deploy those workflows.
 
But unfortunately from the 2nd time, activation of Workflows feature only means the Workflows feature itself. This is because OffWfCommon remains activated. So it works like this.
  • Workflows features will deploy globally reusable workflows in wfpub when activated…
    But wfpub is not there. So empty folders are generated to cover up.

Expected:

 image.png

Actual:
image.png

 

Resolution:

-Deactivate the “Workflows” site collection feature.

-Remove Wfpub folder from “_catalogs” – SharePoint designer

-Toggle the OffWfCommon feature

  • Connect to PNP site collection and run below cmd,

      Disable-PnPFeature -Identity c9c9515d-e4e2-4001-9050-74f980f93160 -Scope Site

      Enable-PnPFeature -Identity c9c9515d-e4e2-4001-9050-74f980f93160 -Scope Site
-Now activate the “workflows” feature from UI should bring back the missing OOB workflows.

The above is kindly provided by the Microsoft Tech Community!

“Sorry, this document can’t be opened for editing” error creating a document in Office Web Apps

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

Problem: You receive a “Sorry, this document can’t be opened for editing” error when you try to create or edit an Office document in Office Web Apps.

 

Issue 1:

In some situations, users that are members of Active Directory (AD) Security Groups may be unable to edit documents in the browser. The solution is to ensure the User Profile Service Application (UPA) is properly configured and fully synchronized with user and group memberships. For more information, see the KB article SharePoint 2013 Unable to edit Office Web Apps 2013 files with users that are members of security groups.

 

Issue 2:

This error will also occur if co-authoring is disabled on the web application. For more information, see the KB article Disable co-authoring in SharePoint Server. Make sure that co-authoring is enabled ($web.DisableCoauthoring = $false) on web applications using Office Web Apps.

 

 

asnp *sh*

##RUN THIS TO SEE WHAT STATE IT SET TO
$web = Get-SPWebApplication <webapplication>
$web.DisableCoauthoring

##RUN THIS TO SET CO-AUTHORING TO ENABLED
$web = Get-SPWebApplication <webapplication>
$web.DisableCoauthoring = “False”
$web.Update()

 

 

Note: Disabling co-authoring via PowerShell ($web.DisableCoauthoring = “True”) will break Office Web Apps functionality for Microsoft Word. Microsoft Word Web Application requires Co-authoring to be enabled to function properly and is enabled by default.

 

For more information see: Configure Office Web Apps for SharePoint 2013

The above is kindly provided by the Microsoft Tech Community!

WFM Certificate renewal process for SharePoint 20132016

Am a keen follower of Microsoft's SharePoint Blog and proud to provide this direct from the Microsoft Tech Community:

Below is a Sample for 1 Node WFM farm using WFM/SB certificate generation key – resetting expired certificate process:

  1. In order to reset generation key for WFM and SB the following steps needs to be done:

System date and clock of WFM node must be set back before certificate expiration date (step needs to be done if multiple WFM nodes in farm)

  1. Ensure you have credentials for WFM Run-As service account and WFM passphrase for generated certificate.

 

  1. In order to reset generation key for WFM and SB the following steps needs to be done WFM node:

System date and clock of WFM node must be set back before certificate expiration date (step needs to be done if multiple WFM nodes in farm)

 

  • Stop Windows Time Service
  • Change System date and clock to Day before certificate expired

 

Steps to follow once System date and time has been set prior to expiration date: 

  1. Output workflow manager powershell commands to clipboard and paste to notepad:

 

////Workflow Manager Powershell results – use “|clip” parameter to output results to clipboard and paste to notepad

 

Get-WFFarm | clip

Get-SBFarm | clip

Get-SBNamespace |clip

 

** “Get-SBNamespace” command will list ManageUser accounts – one of those accounts should be the logon credentials used. Account should have the required SQL permissions to reset expired certificates.

 

  1. Run below commands – reverting date and time should display all services are “Running” before proceeding to next steps:

Get-WFFarmStatus

Get-SBFarmStatus – There are scenarios where Service Bus Message Broker service will get stuck at “Starting”, regardless continue to next step

 

 

  1. From Administrative SharePoint Management Shell, run below command to get current WorkflowHostURI used to register WFM to SharePoint:

$wfProxy = Get-SPWorkflowServiceApplicationProxy           

$wfProxy.GetWorkflowServiceAddress((Get-SPSite -Limit 1 -WarningAction SilentlyContinue))

 

  1. Run below WFM powershell command to change passphrase and thumbprints:

$CertKey=convertto-securestring ‘PASSPHRASE’ -asplaintext -force;

Set-WFCertificateAutoGenerationKey –Key $CertKey

Set-SBCertificateAutogenerationKey –Key $CertKey

 

Then run:

Stop-SBFarm

Update-SBHost

 

  1. Run Workflow Manager Configuration Wizard – leave WFM farm first and then rejoin WFM farm

 

  1. Enable Windows Time Service – this will automatically change server back to current date and time

 

  1. SharePoint 2016: Step by Step guide to add Workflow Manager Certificate into SharePoint trust

https://social.technet.microsoft.com/wiki/contents/articles/34451.sharepoint-2016-step-by-step-guide-to-add-workflow-manager-certificate-into-sharepoint-trust.aspx

 

  1. Export WFM Client certificate using below command from Workflow Manager Powershell:

Get-WFAutoGeneratedCA

 

  • Above command creates “AutoGeneratedCA.cer” file in path where command was executed – default C:Program FilesWorkFlow Manager1.0

 

  1. Copy “AutoGeneratedCA.cer” file to all SP nodes and Web Frontends – install certificate to Trusted Root Certification Authorities certificate store

 

  • Reset IIS on WFEs

 

  1. Register WFM to SharePoint –

 

Sample command:

Register-SPWorkflowService –SPSite “http://FQDN” –WorkflowHostUri “http://FQDN:12291” -AllowOAuthhttp -force

 

  1. From SharePoint Central Admin, run daily timer “Refresh Trusted Security Token Services Metadata feed [Farm job – Daily]”
  2. Test 2013 workflow

The above is kindly provided by the Microsoft Tech Community!