Copilot: Self-Service Purchase coming soon

on
According to the message center Microsoft will roll out the new license request feature and self-service purchase option for Microsoft 365 Copilot by the end of March. These features will be available to users with various Microsoft 365 plans, including E1, E3, E5, and standalone products. Both features will be integrated within Microsoft 365 apps, such as Copilot Chat. The License Request feature I find quite beneficial, as it empowers end-users to justify their usage and request access. At least as long as the organization is already rolling out Copilot to their employees. However, the Self-Service Purchase option may raise concerns for organizations that are not yet prepared to deploy Copilot. It is advisable for all organizations to review their self-purchase settings and make decisions to allow or deny access based on their readiness state. License Request: This feature allows users to request a Microsoft 365 Copilot license directly from their admin. It helps efficiently assign ...

Get-DnsAndIp.ps1 v1 released

on
After troubleshooting my share of deployments, only to fins out there was a DNS record or two missing, made me think of a way to check a DNS server for "all" the required records for a specific deployment.

I have tried different ways to discover and check for name to IP resolution techniques in Powershell, but none of the first attempts were any good. Then I had the task of doing yet another health check, and I decided there had to be a better way to do my research of the DNS deployment.

Finally I discovered the Resolve-DnsName cmdlet, which created an output I could easily work with within powershell. The the rest was the matter of finding out what to look for.

My script doesn't gather everything, but most of the FQDN's I'm used to work with (suggestions for other fqdn's are welcome),

As of the first release, the script will look for the following in a deployment (script must be run with a right to read the CsConfiguration, and must be able to reach the designated DNS servers):

  • Configured Pools 
  • Configured Servers    
  • SIMPLE URLS deployed Internally    
  • SIMPLE URLS deployed Externally    
  • Internal web URL    
  • External web URL    
  • Edge Service FQDNs    
  • WacServer URL deployed Internally    
  • WacServer URL deployed Externally    
  • LyncdiscoverInternal    
  • Internal Lyncdiscover for Mobility       
  • External Lyncdiscover    
  • Internal _sip._Tls resource records        
  • External _sip._Tls resource records     
  • Sip Federation resource records    
  • Sip record internally    
  • Sip record Externally    
  • XMPP resource records

Please read the post on Technet for a more comprehensive description.

As always, the script can be downloaded from the Technet Gallery