Complete details, demo and specifications of the Surface Hub 2S can be found below:

• Behind the design: Surface Hub 2S - https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/Behind-the-design-Surface-Hub-2S/ba-p/464099
• What is the Surface Hub 2S? - https://www.youtube.com/watch?v=pbhNngw3a-Y&feature=youtu.be
• Surface Hub 2S advances Microsoft’s vision to empower teams in today’s modern workplace - https://blogs.windows.com/devices/2019/04/17/surface-hub-2s-advances-microsofts-vision-to-empower-teams-in-todays-modern-workplace/

References:

• Behind the design: Surface Hub 2S - https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/Behind-the-design-Surface-Hub-2S/ba-p/464099
• What is the Surface Hub 2S? - https://www.youtube.com/watch?v=pbhNngw3a-Y&feature=youtu.be
• Surface Hub 2S advances Microsoft’s vision to empower teams in today’s modern workplace - https://blogs.windows.com/devices/2019/04/17/surface-hub-2s-advances-microsofts-vision-to-empower-teams-in-todays-modern-workplace/

Dual Stack IPv4/IPv6 Connectivity allows you to bring your private IPv6 space into Azure and enables connectivity over IPv6 within your Virtual Networks.  This enables you to address IPv4 depletion, meet regulatory requirements and expand into the growing mobile and IoT markets with your Azure-based applications.

IPv6 is used by:

• Government or customers in highly regulated industries
• Internet-of-Things applications that leverage the enormous number of IPv6 addresses available
• Customers who want native (not translated) connectivity from their Azure applications to IPv6 mobile devices 
• Customers who deploy service instances in Azure with dedicated per-customer connectivity
• Customers moving to the cloud (or hybrid) struggling with exhaustion of their IPv4 space and inability/expense of acquiring more IPv4. 

Dual Stack VNET also:

• Builds on long-established Azure VM-to-Internet IPv6 connectivity
• Enables fully IPv6 architectures to be hosted in Azure with IPv6 connectivity between VMs in a VNET, using IPv6 Network Security Group rules, IPv6 User-defined routes and load balancing across VMs
• Allows Azure customers to define their own IPv6 address space to meet the needs of their applications or customers
• Provides “Dual Stack Upgrade-in-place” - where customers can add IPv6 connectivity to their existing applications without re-deploying
• Provides maximum service deployment flexibility - a single service instance can connect with both IPv4 and IPv6-capable Internet clients
• Dual Stack connectivity will preview globally in all Azure Public cloud regions, so you can try it out in a region that is convenient for you.

References:

• Public Preview: Microsoft adds full IPv6 support for Azure VNets - https://azure.microsoft.com/en-us/updates/public-preview-microsoft-adds-full-ipv6-support-for-azure-vnets/

We are excited to announce the general availability of Azure Cost Management features for all Pay-As-You-Go and Azure Government customers.

Cost Management greatly enhances your ability to analyze and proactively manage your cloud costs.  These features will allow you to analyze your cost data, configure budgets to drive accountability for cloud costs, and export pre-configured reports on a schedule to support deeper data analysis within your own systems.  This release for Pay-As-You-Go customers also provides invoice reconciliation support in the Azure portal via a usage csv download of all charges applicable to your invoices.

Azure Usage Download for invoice reconciliation

• As a part of this general availability for Pay-As-You-Go customers, we are now providing usage download capabilities in the Azure portal. This downloadable csv file can be used to reconcile your charges with your monthly invoice.

Cost analysis

• This feature allows you to track costs over the course of the month and offers you a variety of ways to analyze your data. To learn more about how to use Cost Analysis, please visit our documentation, “Quickstart: Explore and analyze costs with Cost analysis.”

Budgets

• Use budgets to proactively manage costs and drive accountability within your organization. To learn more about using Azure budgets please visit our documentation, “Tutorial: Create and manage Azure budgets.”

Exports

• Export all of your cost data to an Azure storage account using our new exports feature. You can use this data in external systems and combine it with your own data to maximize your cost management capabilities. To learn more about using Azure exports please visit our documentation, “Tutorial: Create and manage exported data.”

References:

• Azure Cost Management now generally available for Pay-As-You-Go customers! - https://azure.microsoft.com/en-us/blog/azure-cost-management-now-generally-available-for-pay-as-you-go-customers/
• What is Azure Cost Management? - https://docs.microsoft.com/en-us/azure/cost-management/overview-cost-mgt
• Azure Cost Management Best Practices - https://docs.microsoft.com/en-us/azure/cost-management/cost-mgt-best-practices

There are times you are working with an end user, and they need assistance from their company admin. Within Microsoft Support, if your following our strict security practices and data protection, you should not be giving out any information about their administrators.

I have written this script that comes in handy in these rare cases. This script does everything it needs to do even if the end user is not familiar PowerShell.

• It will self-install Azure AD PowerShell if not already installed
• Connect to Azure AD PowerShell
• Output a list of their Azure AD Company Administrators

Save the following script content to a .ps1 file like so…

Get-AadCompanyAdmins.ps1

And all the user has to do is double click on the file.

Script Content…

# ##########################################################

# HELPER FUNCTION

# ##########################################################

Function PressAnyKey ($message)

{

# Check if running Powershell ISE

if ($psISE)

{

Add-Type -AssemblyName System.Windows.Forms

[System.Windows.Forms.MessageBox]::Show("$message")

}

else

{

Write-Host "$message" -ForegroundColor Yellow

$key = [System.Console]::ReadKey().Key.ToString()

}

}

# ##########################################################

# MAIN

# ##########################################################

# Check if Azure AD PowerShell is installed

$module = Get-Module -ListAvailable -Name AzureAd

$modulep = Get-Module -ListAvailable -Name AzureAdPreview

# Install Azure AD PowerShell if not installed

if (-not $module -and -not $modulep) {

Write-Host "Azure AD PowerShell module not installed!" -ForegroundColor Yellow

Write-Host "Attempting to install Azure AD PowerShell module..." -ForegroundColor Yellow

Install-Module AzureAd

}

# Connect to Azure AD PowerShell

if (-not $AadSession) {

$AadSession = Connect-Azuread -verbose

}

# Get List of Company Administrators

$filename = "admins.of.$($AadSession.TenantDomain)"

$role = $null

$role = Get-AzureADDirectoryRole -Filter "DisplayName eq 'Company Administrator'"

$admins = Get-AzureADDirectoryRoleMember -ObjectId $role.ObjectId | Select-Object DisplayName, UserPrincipalName

# Export list of admins to a CSV

$admins | Export-Csv "$filename"

# Output list of admins

$admins | format-table

PressAnyKey -message "Press any key to continue..."

I have had a couple reports that this script did not work for them.

To make this work, change the following line from…

$role = Get-AzureADDirectoryRole -Filter "DisplayName eq 'Company Administrator'"

To…

$role = Get-AzureADDirectoryRole | Where-Object {$_.displayName -eq 'Company Administrator'}

Turns out -Filter parameter is only available in the AzureAdPreview module.

Did you know you can run PowerShell on macOS and Linux based operating systems?

I know other Tip of The day posts kind of hinted this was possible, but I figured I wanted to call this one out specifically. I just learned this myself a few months back and it has come in handy.

For the macOS…

https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-core-on-macos?view=powershell-6

for Linux…

https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-core-on-linux?view=powershell-6

Did you know if you’re a quest user in another Azure Active Directory or Office 365 tenant, you can leave it any time?

Check out the following article to learn more…

https://docs.microsoft.com/en-us/azure/active-directory/b2b/leave-the-organization

Now you know!

However, if your user account is disabled in their organization, you won't be able to leave it. You will still have to contact one of their admins.

Azure AD access control for Azure Storage has been released as General Availability. Organizations can now grant specific data access permissions for Azure Storage Blob and Queue services to their work or school and service principal identities from their Azure AD tenant using Azure’s Role-based access control (RBAC).

The following are only snippets of the official announcement here…

https://azure.microsoft.com/en-us/blog/azure-storage-support-for-azure-ad-based-access-control-now-generally-available/

Administrators can then track individual user and service access to data using Storage Analytics logs. Storage accounts can be configured to be more secure by removing the need for most users to have access to powerful storage account access keys.

By leveraging Azure AD to authenticate users and services, enterprises gain access to the full array of capabilities that Azure AD provides, including features like two-factor authentication, conditional access, identity protection, and more. Azure AD Privileged Identity Management (PIM) can also be used to assign roles “just-in-time” and reduce the security risk of standing administrative access.

RBAC for Azure Resources can be used to grant access to broad sets of resources across a subscription, a resource group, or to individual resources like a storage account and blob container. Role assignments can be made through the Azure portal or through tools like Azure PowerShell, Azure CLI, or Azure Resource Manager templates.

Today’s tip provides you a little bit of a preview of things to come on the newly updated Networking Blog page. Recently, articles containing outdated information were removed when the blog was migrated to its new home. One example was a series of much loved deep-dive articles on Virtual Machine Queue (VMQ). I’m happy to report that work is ongoing for a completely updated set of articles on this topic and more.

While we wait, let’s look at one of the implementation recommendations you can expect to see.

Background reading on the technologies discussed in today’s tip:

• Virtual Machine Queue (VMQ)
• Receive Side Scaling

The dilemma:

We’ve seen people recommend that RSS be disabled when setting up VMQ.  One statement you can expect to see in the first VMQ article (link coming soon) is that this is no longer supported.

We do not support disabling RSS for a couple of reasons:

1. Disabling RSS disables it for every adapter. Any adapter not attached to the virtual switch can use RSS and as such would be negatively impacted by this change.
2. As you’ll see in future articles, there is a budding friendship between these two technologies. They’ll soon become fast friends...like Peanut Butter and Jelly, Wooster and Jeeves, or Chopin and Liszt.

Important: Disabling RSS is not a supported production configuration on Windows. RSS can be temporarily disabled by Microsoft Support recommendation during troubleshooting for the purposes of verifying whether there is an issue with the feature. In the rare case where RSS causes a problem, the root cause of the issue needs to be addressed. RSS should not be left permanently disabled as it would leave Windows in an unsupported state.

Keep an eye out on the Networking Blog page for more to come.

You may have seen tips on this subject in the past, but let’s see where we are at today!

To Begin With, What is LEDBAT?

LEDBAT (Low Extra Delay Background Transfer) is a latency optimized, network congestion control provider. As a scavenger protocol, it is designed to automatically yield bandwidth to users and applications, while consuming any available bandwidth for background transfers when the network is not in use.

• When increased latency is detected (indicating that other TCP connections are consuming bandwidth) it reduces its own consumption to prevent interference.
• When latency decreases LEDBAT ramps up, consuming the unused bandwidth.

In other words, you can transfer SCCM Packages or Microsoft Updates without interfering with critical application traffic.

Things To Remember About LEDBAT

Use Cases

• LEDBAT can be enabled on a SCCM distribution point running Windows Server 2019.
• LEDBAT can be configured for WSUS servers using NetTransportFilters (see more below)
• BITS is also using LEDBAT for background uploads.
• Current Insider Preview builds have added support for use of LEDBAT by Delivery Optimization.

Configuration Notes

• LEDBAT can optimize any TCP sender-side workload.  It is not limited to updates!
• Congestion providers are configured per-flow:
  • LEDBAT provides congestion control for background traffic flows.
  • It does not compete with or replace congestion providers such as CUBIC, which are used for foreground traffic flows.
• Configure LEDBAT using the Internet Custom template. Never enable LEDBAT using the DataCenter template.
  • This is a common configuration error that can cause LEDBAT to get stuck in slow-transfer-mode, preventing it from ramping up to leverage unused bandwidth.
  • For more on this issue and how to properly configure LEDBAT, see Support for LEDBAT: Public Service Announcement
  • Transport Filters can seem somewhat mystical until you dive in and see how simple they really are. Advanced Users, see TCP Templates for Windows Server 2019 – How to tune your Windows Server Transports for an easy to understand explanation.
• LEDBAT has been backported to Windows Server 2016 (kb4132216,4284833)

Are you interested in Azure AD development or work with customers who are trying to integrate their app to Azure AD?

We have a blog. Check it out at https://blogs.aaddevsup.xyz/

We try to blog about common questions and issues that we see come into our support channels. This includes topics about our Authentication libraries such as Active Directory Authentication Library (ADAL) or Microsoft Authentication Library (MSAL), and working with our Azure AD related APIs such as Azure AD Graph or Microsoft Graph API.

If you have any ideas on what you would like us to blog about, let the Azure AD Developer Support team know @ AADDEVTeam@microsoft.com