SKILLS & TRICKS
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)
According to the documentation of Azure CLI you need to use az storage message put.
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:
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:
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.
Why use Azure Migrate?
Azure Migrate helps you to:
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:
When you create a new Office 365 group, there will be an associated SharePoint Team site is created automatically. In this case, we need a new Group with an existing team site. To start with, make sure connect to Office Group is enabled at tenant level.
Login to SharePoint Online Admin Center >> Click on Settings from left navigation. In settings page, under "Connections from sites to Office 365 groups", Set "Allow site collection administrators to connect sites to new Office 365 groups".
Now, you can connect your SharePoint Online sites to Office 365 groups. To connect an existing SharePoint Online site to new a Office 365 group, follow these steps:
Login to SharePoint Online site collection with Site collection administrator rights >> Click on the Settings gear icon >> Select "Connect to new Office 365 group". You are now presented with overview page about a quick explanation of what will be created by Office 365 for your site collection what's going to happen by connecting your site to an O365 group. Click on "Let's get started"
We all know that Get-SpoSite cmdlet contains more than one parameter set and you may only use parameters from one parameter set and you may not combine parameters from different parameter sets. Moreover, it retrieves and returns properties of all site collections that match the given criteria.
But sometimes you run into weird issues when you are doing the most common things. In this case, one of my friend was cleaning up his demo Office 365 tenant. To make an overview of all site collections, he ran the following cmdlet:
This would make a list of all site collections that are available in Office 365 tenant and export it to a CSV file. When going through it, he noticed that none of the site collections were flagged as a hubsite. This couldn’t possibly be true as he created many hub sites for testing purposes.
I decided to check this in my own tenant to see if it was a local problem. So let’s see what happens.
Running the following PowerShell returns all site collections that contain the word intranet.
Since ASP.NET Core 2.2 was released I have been working on getting all my different applications updated and using in-process hosting. I pretty quickly hit an issue with an application that uses SQLite. As soon as the application tried to access the database I ended up with the following error.
SqliteException: SQLite Error 14: ‘unable to open database file’. Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(int rc, sqlite3 db) Microsoft.Data.Sqlite.SqliteConnection.Open() Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenDbConnection(bool errorsExpected)
Issue and Work Around
After some Googling, I found an issue on GitHub that details the problem. It turns out that when the application gets its current directory it is returning the path to the IIS process that is hosting the application instead of the directory when the application is.
On another GitHub issue, I found a link to a recommended workaround. Add the following class somewhere in your application. This code comes here.