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!


 

What’s New in Excel for the web

What’s New in Excel for the web

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

Delivering rich, delightful experiences to our customers continues to be a top priority for our Excel team. A few weeks ago, we shared how to easily format your data with color and style, and more. Today, we bring you a set of new features and improvements to help you better analyze your data, specifically:



  • Text to columns

  • PivotTable improvements

  • Sort improvements

  • Interactive charts

  • Additional keyboard shortcuts


 


Text to columns


You can now split text into columns using delimiters.  For example, with a few clicks, you can convert “Hello World” in one cell to “Hello” and “World” across two adjacent cells. 


 


You can also select multiple delimiters including tab, semicolon, comma, space, and custom [delimiter] at the same time.  For example, “Hello, how are you?” in one cell would split into “Hello”, “”, “how”, “are”, and “you?” across 5 cells if you selected both comma and space as delimiters.


 


Text to columnsText to columns


 


PivotTable improvements


Analyze your data with the new and improved PivotTable experience in Excel for the web including:



  • Create a PivotTable quickly with Recommended PivotTables 

  • Change the settings and look-and-feel of your PivotTable the way you want it via the new PivotTable ribbon including PivotTable Styles and new PivotTable Settings task pane

  • Copy, refresh, and show or hide PivotTable task panes with one click using the new PivotTable right click menu


 



 


 


Sort improvements


Sorting is fundamental in data analysis.  Sorting can be more than numerical or alphabetical ordering though.  In Excel for the web, you can now sort by Cell Color, Font Color, and Conditional Formatting Icon, in addition to Cell Values.  Furthermore, you can sort by more than one column.


 


Sort improvementsSort improvements


 


Interactive charts


You can now directly select and interact with chart elements when formatting a chart. Double-clicking a chart element launches the format task pane while single-clicking a chart element navigates you to its corresponding formatting options. In addition, non-data chart elements can now be removed from the chart using the delete/backspace keys. You will also be able to see a preview of your selection as you hover your mouse cursor over different chart elements.


 


Interactive chartsInteractive charts


 


Additional keyboard shortcuts


Many users have asked for additional well-known and commonly used keyboard shortcuts in Excel for the web, and we’re thrilled to bring you:



  • End-arrows – move to the last cell in the row or column

  • Ctrl-End – move to the last cell that contains data or formatting.

  • Ctrl-Shit-End – extend the selection to the last used cell


Also coming soon are



  • PgUp/PgDn – move screen up/down

  • Alt-PgUp – move screen left

  • Alt-PgDn – move screen right

  • Alt-Shift-PgUp – extend selection left one screen

  • Alt+Shift+PgDn – extend selection right one screen


 


Find the full list of keyboard shortcuts via Help > Keyboard Shortcuts.


 


Keyboard shortcutsKeyboard shortcuts


 


These are just some of the latest improvements, many more are coming soon!


 


Your feedback helps shape the future of Excel for the web. Please let us know how you like a particular feature and what we can improve upon—send us a smile or frown.


 


Want to know more about Excel for the web?  See What’s new in Excel for the web and subscribe to our Excel Blog to get the latest updates. Stay connected with us and other Excel fans around the world – join our Excel Community and follow us on Twitter.


 


Thank you!


 


 

Inclusive Learning 365: Designed to Work for Everyone

Inclusive Learning 365: Designed to Work for Everyone

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

Today’s guest post was written by Chris Bugaj, Karen Janowski, Mike Marotta and Beth Poss – Assistive Technology experts, and co-authors of the new book, Inclusive 365


 


Designing experiences that reach all learners is a fundamental need for every educator to engage in. However, adopting an inclusive mindset is necessary before one can design educational experiences that meet every individual’s need. Within an inclusive mindset is the belief that inclusion is feasible, that all learners can achieve their potential, and that we must offer strategies that are flexible, accessible to all and intentionally designed. Inclusive educational experiences rarely happen by accident. Designing for inclusivity acknowledges learner variability and focuses on strengths that promote engagement, success, and autonomy.


 


Ubiquitous integration of educational technology helps create barrier free learning spaces where everyone has access to the tools to succeed and where use of technology supports does not mark any one learner as less accomplished.


 


As we discuss in our forthcoming book, Inclusive Learning 365, technology can be used to design experiences that are flexible which removes obstacles to independence. In the spirit of building inclusive learning experiences, Microsoft is paving the way toward ensuring ubiquitous access to inclusive technology for all. They have developed a multitude of features which promote accessibility and inclusion which are built into existing tools such as Office 365 and Windows. They have partnered with educational institutions and other technology providers to ensure these tools are widely available to the masses. Providing familiar tools with a variety of customizable features removes obstacles to content access. These tools offer flexibility and choice so that users can identify the features which work best for them, depending on the task and their own unique learning needs.


NEW orig upate color with calendarv3.jpg


Changing the visual presentation of text, adding audio supports, translation of both voice recordings with text to speech and playback in multiple languages, are just some of the features built into Microsoft’s Learning Tools. Additionally, they have made one of their flagship accessibility tools, Immersive Reader, available to third party developers extending its reach. Immersive Reader makes text accessible for those who are learning to decode by helping them understand what they are reading. An example of that partnership with other developers is how Wakelet and Immersive Reader interact. For a recent immigrant from Israel, whose primary language was Hebrew, this partnership opened the curriculum for him in a way that wasn’t possible previously. The educator curated grade level content using Wakelet. The learner used the embedded Immersive Reader feature to translate the articles from English to Hebrew and then listened to them in his primary language. He independently accessed grade level content. Eventually, this feature was no longer needed as he gained English language skills. But it made a tremendous difference early in the school year.


 


Sometimes, accessibility is as simple as spell check—a tool that most of us do not even think about, as it is seamlessly integrated into almost every digital writing tool used. For one nine-year-old learner, however, spell check has made the difference between feeling hesitant as a student and becoming a confident learner with a newfound love for writing. Knowing that she had difficulty with spelling, she would get hung up on how to spell a word, lose her train of thought and get frustrated, often changing a well thought out and effective word she was writing to a less sophisticated and less interesting word that she knew how to spell. Asking the adults around her to help her spell was typically met with the direction “Try to find it in the dictionary”, not a helpful strategy when you might not be sure of the second letter in the word! When one educator explicitly modeled the simple strategy of clicking on the familiar red squiggly underlined word and using the suggestions to help her correct her misspelling, she found a solution to her writing challenges. When educators instead gave her the prompt of “Do your best and see what suggestions spell check gives you.” she took agency of her own learning. When she realized that even when she was doing handwritten work or filling in a printed worksheet, she could open a Word document and type in the word she was struggling with to copy correctly, she felt successful and proud of her work. A simple, often underrated function of a tool helped change the mindset of one young learner, who now sees herself as capable.


 


If the principal responsibility of an educator is to support the learners they are meant to serve, then every educator should explore both common-place and newer technologies designed with inclusivity and accessibility in mind. Learners, just like this nine-year-old, can be invited to evaluate the features for themselves, develop their own awareness for what’s available, and craft their own technology toolkit for life-long learning.


 


Join the four of us for a free webinar (June 17th @ 1pm PST) led by Mike Tholfsen, as we discuss Inclusive Learning 365.


Chris Bugaj, Karen Janowski, Mike Marotta and Beth Poss

A powerful agent for Azure Monitor and a simpler world of data collection; now generally available!

A powerful agent for Azure Monitor and a simpler world of data collection; now generally available!

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

Today we announced the general availability of the Azure Monitor Agent (AMA) and Data Collection Rules (DCR) that are two brand new features from the Azure Monitor product. You can read more about the specific changes announced on this launch in this update announcement here.


Both these features address the data collection aspects of Azure Monitor, indicated by the red dotted box below. They aim to provide powerful new capabilities, while at the same time ensuring data collection setup is a breeze for users! Read on to find out how…


 


What’s the AMA? Is this “yet another agent”?


The AMA collects monitoring data from the guest operating system of virtual machines and delivers it to Azure Monitor. It is meant to replace all other agents that exist today for a similar purpose, consolidating their features and providing more capabilities on top and enabling long-requested asks by all of you.


 


So, while it is indeed another agent, it’s primary targeted to address the underlying sentiment of this question, which is pain and frustration at “too many agents”. For users today, there’s one agent if you wish to collect telemetry logs data, another agent if you want to collect metrics from Windows machines for alerting, another one if you want to do the same but from Linux machines. I think we all can agree that’s no fun, and the solution to this is (yep, you guessed it), the AMA!


 


Is the AMA the ‘one agent’ for everything?


The answer is no, but it’s meant to be the single agent for uploading data to Azure Monitor going forward, which collects telemetry data and sends it to Azure Monitor Logs or Metrics (today), and Event Hubs, Storage Accounts and many other destinations that you need to send telemetry data to (in future).


Other extensions need to be deployed for specific “curated” monitoring scenarios like security or insights, that all use the AMA to pump data to Azure Monitor.


Thus, it’s important to understand the new extension model that the AMA introduces that reduce management overhead and provide a consistent, easy way to enable, update, debug and remove specific monitoring scenarios.



  • The AMA is available as a VM extension, and so all VM extension capabilities are available out of box like auto-upgrade, no-config installation and more

  • Previously known as ‘Log Analytics Solutions’ or ‘Management Packs’, additional VM extensions may also be installed on the machine for specific monitoring scenarios like security monitoring (Azure Security Centre), SIEM (Sentinel), Virtua Machine Insights, Container Insights, VM Guest Health, Network Monitoring and many more

  • These extensions all use the AMA extension to pipe data to the required destination, so user can choose to selectively install only what’s required. Nothing more, nothing less!


ExtensionModel.png


Okay, what else is new besides consolidating existing feature sets?



  • Centralized yet granular (“resource-centric”) configuration, that allows you to have a setup that works best for your organization using the power of Data Collection Rules (see next section). You can either opt for centralized collection setup (one rule for all machines) as well as granular collection setup (different rule for different set of machines, even though connected to the same workspace)

  • Native to ARM, which means you can use ARM templates, Azure policies, etc to manage monitoring code changes in the same as as your service code, with proper review gates and safe deployment practices

  • Event filtering for Windows Event Logs that allows you to limit data collection to exactly what you require, thus providing tremendous cost saving opportunity


“We are very excited with the new Windows Security filtering capabilities in Azure Monitor Data Collection Rules. During the last 4-5 months, 3 of our customers have used the new feature. They have all gained significant logging cost savings (30-50%) being able to exclude irrelevant security events into their log workspace. The XPath filtering capabilities adds great filtering capabilities on agent level, so we only send the needed data into Azure Log Analytics. Moving forward we are also excited to learn, that Microsoft will continue to enhance the filtering capabilities to support some of the features in newer versions of XPath”


– Morten Waltorp Knudsen, CEO & Cloud Architect, 2LINKIT


 



  • Support for multiple destinations, where you collect the data once and send it to multiple Log Analytics workspaces (multi-homing anyone?), or a combination of logs and metrics destinations at the same time

  • Much better performance in terms of the EPS (events per second) rate, compared to existing agents

  • Seamless experience on Azure and non Azure environments, using Azure ARC as a pre-requisite. The ARC agent comes at no extra cost and is only used to install the AMA and additional VM extensions on your non-Azure machines, the same way it’s done for Azure machines (Hint: One way to manage it all). 


“We have a large investment for both on-premise and cloud resources.  With Azure ARC and Azure Monitor Agent, we are able to collect real-time data from both environments into log analytics to provide analysis, gain visibility from operation management and compliances.  This also allows us to reduce redundant tools, processes, and expenses”


– An avid user from a large US telecommunication company


 


What’s DCR? Why should I bother learning about it?


“I want an easy way to setup monitoring and data collection for all my resources”


“I want to centrally manage what telemetry data I collect, and just do it one way for all instead of managing it differently per machine or resource type”


“I want a single pane of glass view for any/all data being collected from my resources and how/where it’s being sent to”


“I want a simpler monitoring life! :)”


If you can relate to any of the above, then Data Collection Rules is here to help!


Simply put, a DCR is a rule you can use to define what data to collect, how it should be processed, and where it should be sent to. It’s agnostic of the source of the data as well as the destination, making it independent of either and thus flexible enough to configure collection just the way you need to.


As such, DCR presents tremendous opportunity to revisit and simplify your existing data collection setup, and provides freedom from all existing limitations around configuration to make the most out of Azure Monitor!


shayoni_seth_2-1623624703192.png


 


How do DCRs work with AMA?



  1. You first create a DCR which is nothing but an Azure ring 1 resource, which resides within Azure in a resource group and subscription of your choice (same as any other resource)

    1. In the DCR, you select which types of data you’d like to collect from what’s supported today

    2. Finally you specify the destination(s) where the data needs to be sent to. Within a single DCR, you can specify multiple Log Analytics workspaces today or a combination or logs and metrics destinations in Azure Monitor. Note: The metrics destination is not GA and continues to remain in preview with these limitations



  2. Once created, one or more DCRs can be applied to one or more machines using DCR-Association (or DCRA) which need to be deployed per machine (1:1 mapping between DCRA and resource)

  3. These machines should have the AMA installed which then polls into new Azure Monitor Control Service to fetch the DCRs the machine is associated with. Once received, AMA starts collecting the required data

    1. AMA uses Managed Identity so the machines should have that enables. See prerequisites here.




Note: When using the DCR creation experience on Azure Portal (shown below), you only need to perform step #1. All other steps are performed on your behalf (woohoo, no need to worry about agent installation!)


 


dcr-sample.png


 


 


Does it only support AMA?


As of today, DCR is used to configure what the AMA should collect and where the data should be sent to. In the long term though, Data Collection Rules will become the single, consistent way to configure data collection for other resources like PaaS services (uses Diagnostic Settings today) or application (uses AppInsights SDK today), and whatever else that you need. Tell us now and help us build it for you!


 


What’s the migration story from existing agents?


We will not be auto migrating customers due to the fact that AMA is not at full parity yet with the existing agents.



  • Log Analytics Agents customers may start migrating to AMA if their required set of capabilities and “solutions” are available already. Migration can be performed using the same steps listed in our documentation today, and using policies to replicate these steps “at scale”

    • In addition, ensure to cleanup existing agents, workspace keys, config files from machines

    • Also disable solutions on workspaces that you wish to use the new agent for instead



  • Azure Diagnostic Extension and Telegraf agent customers can start migrating to AMA if they only need to send metrics data to Azure Monitor Metrics. Sending data to Event Hubs and Storage accounts is not supported yet.


We will be releasing migration tools in the coming months to automate and simplify some of this for you. In the meantime, if you need additional guidance or have questions, please reach out to the product group directly. We would be happy to assist!


 


What’s next?


This launch is just the first step towards a better and more powerful world of data collection for monitoring.


On the agent side:



  • We continue to consolidate features from existing agents, including but not limited to:

    • Custom log collection

    • Windows 10 support

    • New destinations like event hubs and storage accounts



  • Support for popular solutions (AMA extensions) that you use today. This should unblock more of you to migrate soon to the better agent.


On the DCR side, we will expand scope to act as the control plane for other parts of Azure Monitor data collection, like API based ingestion and Diagnostic Settings.


Lastly, we rely on you to tell us where we should head next. So tell us what you need, and tell us now!