Did you know? Automated diagnostics are available to troubleshoot various Office 365 issues.

Did you know? Automated diagnostics are available to troubleshoot various Office 365 issues.

This article is contributed. See the original author and article here.

Seeing that this is a relatively new development, I wanted to share information about automated diagnostics that customers can run inside of the Microsoft 365 admin center. The goal of these is to help you to solve various support-related issues that you might encounter, without having to open a support ticket.


Currently, the way to interact with available diagnostics is via the Need help? button in the Microsoft 365 admin center:


diagnostics01.jpg


There are a few things you might see when you search in the text field that will come up; for example:


Let’s say you’d like to increase the Exchange Web Services (EWS) throttling setting for your tenant to be able to use a 3rd party migration tool when moving to Exchange Online. If you search for “EWS” you’ll see an auto-suggested option that says “Increase EWS Throttling Policy”. If you choose that, there are several sections that you will see:


diagnostics02.jpg


The sections you might get will vary based on your search, but let me explain the 3 that are shown in the screenshot:



  • Section 1: the Diagnostics section and the button indicate that there are diagnostics associated with your query; pressing that button will run these diagnostics, which might require additional choices until the action is completed. Not all queries will result in diagnostics (there are over 50 of them currently with more coming, but there are many more possible questions!)

  • Section 2: the Insights section is the explanation of what you can do to get help with your query. There are many more Insights than there are Diagnostics. When there is a diagnostic, the insight will typically relate to the shown diagnostic.

  • Section 3: this section provides ‘top search results’ based on your query.


Recommended articles are usually a ‘wider net’ used to try to answer your question. Insights are targeted to what you typed (there are 100s of these, made for the most frequent things our customers search for). Diagnostics are the most targeted and typically allow you to take specific action without leaving the “Need help?” section.


Which Exchange and Outlook diagnostics are available?


Seeing that this is the Exchange blog, here is a link to the article that lists currently available related diagnostics:


Self-help diagnostics for issues in Exchange Online and Outlook


But wait, there is more!


Various other teams (including SharePoint, OneDrive and Teams) have also created diagnostics and documents listing what is available.


An additional very cool and new initiative is Diagnostics for Social Good, where Microsoft will donate a percentage of realized support savings to charity. To read about this new initiative and see information about SharePoint, OneDrive, and Teams diagnostics, please see Diagnostics for Social Good.


If you have feedback about these diagnostics or insights, please comment below!


Nino Bilic

Azure Purview Integration Runtime

Azure Purview Integration Runtime

This article is contributed. See the original author and article here.

Introduction


Azure Purview is a unified Data Governance tool used to manage and govern your on-premises, multicloud, and SaaS data. For those of you who have used Azure Purview previously, you will know that to scan sources such as Azure data assets (Blobs, Azure Data Lake Service, etc.) you will need an authentication methodology leveraging either a Purview managed identity or perhaps a service principal. This applies to a wide array of assets, however, there is also a method to use self-hosted integration runtimes (SHIR) that will let you scan data sources in Azure Purview. This is particularly useful to install into your machines when scanning a resource in a private network (on-prem or VNET). One of the top use cases for this is around the scanning of on-prem SQL Servers, which is a frequent ask from customers.


In this blog we will review how to set up a self-hosted integration runtime in Azure Purview and demonstrate how to use it in setting up a scan for an on-prem SQL Server.


 


Background on Self-Hosted Integration Runtimes


The Integration Runtime (IR) is compute infrastructure used by Azure Data Factory to provide data integration capabilities across different network environments. You can set a linked service which defines a target data store or a compute service along with a defined activity. The IR is the bridge between the activity and linked service and provides the compute environment where the activity either runs on or gets dispatched from. There are several types of Integration Runtime (IR) but we will be focusing on Self-hosted integration runtimes.


 


Walkthrough


 



  1. First navigate to the Management Center in the Purview Studio and select Integration Runtimes.


 


Arvind_Chandaka_0-1621884659775.png


 


 



  1. Select New at the top, select Self-Hosted and press Continue.


 


                 


Arvind_Chandaka_1-1621884659784.png


 



  1. Enter the name that you want for the Integration Runtime along with any description you would like to add and click Create.


 


Arvind_Chandaka_2-1621884659788.png


 



  1. Then follow the steps for the Manual setup. Make sure to download and install the integration runtime into the self-hosted machine where you want to run it.


Arvind_Chandaka_3-1621884659790.png


 



  1. Navigate through the Setup Wizard to install the Integration Runtime


 


Arvind_Chandaka_4-1621884659797.jpeg


 


 


Arvind_Chandaka_5-1621884659805.jpeg


 


 



  1. After finishing this you will have to insert the authentication key in step 4 into the input box shown in the image below. You will not need to change the proxy.


 


Arvind_Chandaka_6-1621884659813.jpeg


 


 



  1. After the key is verified, go ahead and register the runtime. Verify the information regarding the node name and click finish.


Arvind_Chandaka_7-1621884659819.jpeg


 


 


Now that you have set up the SHIR on-premises, you can use it to bring certain sources into Purview. We will demonstrate this with the scanning of SQL Server on-prem.


Now we will assume that you have a SQL Server with access to the master database and we can authenticate using SQL authentication – for more information on this see https://docs.microsoft.com/en-us/azure/purview/register-scan-on-premises-sql-server#storing-your-sql-login-password-in-a-key-vault-and-creating-a-credential-in-purview to ensure that you have the right credentials formulated and stored accordingly. This is highly important for the scan to work.


.



  1. Navigate to Azure Purview and Register a SQL Server source


 


Arvind_Chandaka_8-1621884659830.png


 


 


 



  1. Make sure to enter the name of the source along with the Server endpoint


 


Arvind_Chandaka_9-1621884659836.png


 



  1. After this, configure your scan by entering the following information on Scan name, selection of the Integration Runtime we have created from earlier, Server endpoint (which should already be filled in), and the credential for SQL Authentication. Continue through and run through the scan similarly to other sources by selecting the rule sets and recurrences.


Arvind_Chandaka_10-1621884659840.png


 


 


Congratulations! You have now set up your Integration Runtime and can scan through SQL Servers and much more!


 


 

New webinar series: Monthly threat insights

This article is contributed. See the original author and article here.

We’re happy to announce a new monthly webinar series called “monthly threat insights”. On the third Wednesday of each month, the Microsoft Defender Threat Intelligence team will dive deep into a selected emerging threat as seen in the threat analytics library available in Microsoft 365 Defender. Using the threat analytics report authored by Microsoft security researchers and analysts, we’ll examine the different facets of the threat: its history, behavior, and detection details, as well as a detailed MITRE ATT&CK framework mapping of attack techniques and recommended mitigations. We will also look at KQL queries you can use in advanced hunting to investigate the threat on your own.


 


If you use one of the Microsoft Defender products, you will also have access to the full report in the threat analytics page of Microsoft 365 Defender. In this page, you can access the report, see alerts associated with this threat, and determine if you have applicable protections in place.


 


Be sure to register using this link, and join us every third Wednesday for these timely and insightful webinars.


 


This Wednesday June 16th at 9AM PST is our first episode; we hope to see you there! 


 


If you can’t join us, we will record these webinars and share them on https://aka.ms/securitywebinars

Microsoft Teams certified accessory tour | Modern Headsets, Speaker, Webcam & Surface Headphones 2+

Microsoft Teams certified accessory tour | Modern Headsets, Speaker, Webcam & Surface Headphones 2+

This article is contributed. See the original author and article here.

Take a look at the latest Microsoft hardware innovations in support of remote and hybrid work at home and in the office. Engineering leader, Branden Powell, joins Jeremy Chapman to show how the new Microsoft and Surface accessories deliver the best experience on Microsoft Teams.


 


Screen Shot 2021-06-15 at 1.09.10 PM.png


 


All our accessories are made with premium materials, so they look great and are built to last. They’re compact and lightweight to optimize your space, no matter where you’re working from. We’ve prioritized all-day comfort and mobility, and everything is certified for use with Microsoft Teams to give you a great online meeting experience. The convergence of hardware plus software helps minimize meeting fatigue, so you can stay fresh and in the flow of your work.


 



 


The latest round of accessories is available today: Surface Headphones 2+ for Business, Modern USB, Modern Wireless Headsets, Modern USB-C Speaker, and the new Modern Webcam.


 





QUICK LINKS:











Link References:





Unfamiliar with Microsoft Mechanics?




 


Keep getting this insider knowledge, join us on social:


































































Lesson Learned #175: Connecting to Private EndPoint of Azure SQL Database from Managed Instance

Lesson Learned #175: Connecting to Private EndPoint of Azure SQL Database from Managed Instance

This article is contributed. See the original author and article here.

Today, I worked on a very interesting case when our customer wants to connect to the Private EndPoint/Link of Azure SQL Database from Azure SQL Managed Instance. In this article, I would like to share with an example how to do it. 


 


Basically, once you have created the Private Endpoint on the VNET/SUBNET of your Azure SQL Managed Instance. The most important thing is to resolve the IP. We have two options:


 



  • Adding in your DNS server the resolution for your Azure SQL Database Private EndPoint IP.

    • For example, servername.database.windows.net points to 10.1.2.5. If you have already deployed you Azure SQL Managed Instance before creating this Private Endpoint in order to update the DNS resolution of your Azure SQL Manage Instance nodes, I would like to suggest to scale up/down your Azure SQL Managed Instance in order to refresh the DNS servers.



  • Connecting using the IP address of your Private Endpoint.

    • In the Linked Server definition, type a name (for example, MyLinkedServerWithPrivateEndpoint), choose any provider in the data source type the Private Endpoint IP that you have, for example, 10.1.2.5 and finally, in the catalog type the name of your database. 

    • For login credentials, you need to specify:


      • UserName: myloginname@servername (without adding .database.windows.net)

      • Password: Type the password of this login.






 


LinkedServer.png



LinkedServer2.png



In this situation, everytime that you run a query, for example, SELECT * FROM MyLinkedServerWithPrivateEndpoint.DatabaseName.SchemaName.TableName you are going to directly to the Private Endpoint. This applies for Azure SQL Database and Azure Synapse. 


 


Enjoy!