​We know that renaming a Channel in Teams breaks the associated SharePoint link. It creates a new folder in SharePoint but when you access the files from Teams, it takes you back to the original folder.  Confusing and messy!!

However, I have a process to rename a Channel in Teams without breaking the link to SharePoint.

Before I change things, I want to show how my current Team is setup.

​We all know by now that we can invite guests in Microsoft Teams if the settings are in place.  Well, that depends on how settings are configured in your tenant.

As you can see that guest access is enabled in Microsoft Teams Admin Portal.  And, yes, this setting has been enabled for several weeks.

​When Teams owners or members invite guests from public Teams, they get this message:

​Teams owners share the same experience as the image above when trying to invite guests from private Teams.

​I ran into something I have not experienced before when creating a new Teams channel.

Aside from not being able to add these special characters (~#%&*{}+/\:<>?|'”..), I discovered that Teams allows only 50 characters for “Channel name”.

In my example below, it truncates “This is a very long channel description with 50 characters” to “This is a very long channel description with 50 ch”

This solution is based on the letsencrypt-webapp-renewer. It uses the same core library than the Azure Lets Encrypt site extension, but it is run as a WebJob. It can (should) be installed on its own web app, and supports multiple target websites.

The author of the letsencrypt-webapp-renewer has made thorough instructions, so I won't copy them here. When granting the service principal rights, you may want to only add Website Contributor and Web Plan Contributor instead of Contributor rights. The only thing needed in addition to those instructions is the support by the web app itself.

As you may already know, the Office 365 Video service is being replaced by Microsoft Stream.  If you have been using Office 365 Video to publish videos, you can now start migrating it to Microsoft Stream using the self-service migration tool. If you don’t see it, you can request to register your tenant using the form available here https://aka.ms/O365VideoEarlyMigration

When you logon to your Office 365 Video portal you will see the migration banner to start the migration process

This will open a new window (https://web.microsoftstream.com/officemigration)

This is one of the most controversial topics of SharePoint Online and everyone seems to have a theory. For some it works like a charm and they never get to experience the pain while others even open up tickets with Microsoft Premium Support and still the issue remain unresolved.

Yes i am referring to the great file attachment and upload sizes. When you go online to look for the right answer, all you get is confusion with out dated information. For example old articles, new ones, One Drive for Business sync tools, classic vs modern and you will get unsure exactly what sizes to recommend to a client. So, I decided to do some testing with various large dummy file sizes around what I was reading the limitations to be. The results were close to Microsoft’s article, but with a very interesting caveat .

There are a few factors when you want to know max file sizes:

• Classic interface
• Modern interface
• List Attachments
• Document Libraries
• Drag and Drop
• Upload Multiple

Lets admit that migration of any sort is a pain and migrating something to the cloud for the first time is always challenging. I have been going through this for quite some time and finally had the chance to play with Azure Migrate and it has been a good experience overall.

​If you plan to go to Azure you will have 2 choices for your current environment:

• Recreate you infrastructure from scratch
• Use Azure Site Recovery to “move” your on-premise VMs to Azure

The goal of this post is to explain you what is Server Migration and how it can help you for your migration to Azure.

​The Azure Migrate service assesses on-premises workloads for migration to Azure. The service assesses the migration suitability of on-premises machines, performs performance-based sizing, and provides cost estimations for running on-premises machines in Azure. If you’re contemplating lift-and-shift migrations, or are in the early assessment stages of migration, this service is for you. After the assessment, you can use services such as Azure Site Recovery and Azure Database Migration Service, to migrate the machines to Azure.

Azure Migrate helps you to:

• Assess Azure Readiness: Assess whether your on-premises machines are suitable for running in Azure.
• Get Size Recommendations: Get size recommendations for Azure VMs based on the performance history of on-premises VMs.
• Estimate Monthly Costs: Get estimated costs for running on-premises machines in Azure.
• Migrate with High Confidence: Visualize dependencies of on-premises machines to create groups of machines that you will assess and migrate together.

​I recently created a Microsoft Office 365 development environment via https://aka.ms/offdp

I was creating an environment to do some SharePoint Modern theming (I created a new Communication Site via the modern Admin interface on my new tenant), but noticed the classic (rather the older) Change the Look interface: