GR

​GR  Read More

​

Hello,

I’m trying to use Microsoft Graph API in PowerShell to create external/local users in our B2C tenant, but I receive the following error: “The domain portion of the userPrincipalName property is invalid. You must use one of the verified domain names in your organization.” There must be a parameter to switch from an internal or federated user to an external one, but I’ve been unable to find it. Any help you can offer would be appreciated! Here is my script:

​Hello,I’m trying to use Microsoft Graph API in PowerShell to create external/local users in our B2C tenant, but I receive the following error: “The domain portion of the userPrincipalName property is invalid. You must use one of the verified domain names in your organization.” There must be a parameter to switch from an internal or federated user to an external one, but I’ve been unable to find it. Any help you can offer would be appreciated! Here is my script: $NewUsers = Import-Csv $NewCSVPathForEach($NewUser in $NewUsers){    $TestTheUser = $null    $TestTheUser = (Get-MGUser -UserId $NewUser.UserPrincipalName -ErrorAction SilentlyContinue).Id     IF ($TestTheUser) {        Continue    }     else {        $PasswordProfile = @{            Password = “Ninja%67#Dangerous”            ForceChangePasswordNextSignIn = $false        }            $UserParams = @{            DisplayName = $NewUser.DisplayName            UserPrincipalName = $NewUser.UserPrincipalName            PasswordProfile = $PasswordProfile            AccountEnabled = $true            MailNickname = $NewUser.MailNickname            identities = @(                @{                    signInType = “emailAddress”                    issuer = “<MyTenant>.onmicrosoft.com”                    issuerAssignedId = $NewUser.UserPrincipalName                }            )            passwordPolicies = “DisablePasswordExpiration”        }        New-MgUser @UserParams    }}  Read More

​

REST API is a cornerstone in the management of resources on Azure, providing a streamlined and efficient approach for executing create, read, update, and delete (CRUD) operations. By leveraging HTTP methods such as GET, POST, PUT, and DELETE, REST API simplifies resource manipulation for administrators. Moreover, REST API’s support for various data formats, including JSON and XML, enhances its versatility, making it indispensable for automating workflows and facilitating continuous deployment and integration practices. Focusing on Azure DDoS Protection, we will delve into its REST API integration, which enables the configuration of plans, association of virtual networks and individual resources, and real-time protection status. This integration is crucial for maintaining robust security in the fast-paced environment of cloud deployments. It ensures that security protocols are not only enhanced but also keep pace with the rapid deployment cycles characteristic of modern cloud infrastructures.

Getting Started

In the following examples, we’ll be using Postman to send our REST API requests to Azure Resource Manager to create, update, and delete the Azure DDoS Protection plan. We’ll also manipulate virtual network and public IP resources to receive DDoS protection status and enable protection for specified resources. For Azure DDoS Network Protection, we will link a virtual network to a DDoS Protection Plan, ensuring that all resources within the virtual network are protected. For Azure DDoS IP Protection, we will enable DDoS protection directly on a public IP without needing a DDoS plan, providing flexibility for individual resources. There are other methods and tools to send REST APIs outside of Postman, such as PowerShell, Az CLI, Swagger, and more. The basics will be the same regardless of the tool or method used, just our interface will be different. To follow along, check out the prerequisites below to get started.

Prerequisites:

Link to download Postman: Postman API Platform | Sign Up for Free
Link to blog that covers how to prepare your identities and Postman tool to send REST API commands: Azure REST APIs with Postman (2021) | Jon Gallant

If you’re following along and have followed the prerequisites, you should now have your Postman Collection configured to something similar as below. Our first screenshot shows the Authorization tab in the Postman Collection. We’re going to use the Auth Type of Bearer Token and use the variable from our variables tab.

Next, we have our pre-request script that you can grab from the linked blog above. This script is needed to send the requests continuously to Azure Resource Manager.

Lastly, we have our variables defined to use in our Postman Collection.

With our Postman profiles configured, we can begin managing Azure resources outside of the Azure Portal in a quick and seamless manner. When sending a REST API request, there are mandatory fields that need to be present, depending on the type of request sent. To create a new Azure DDoS Protection plan or to update an existing one, we’ll need to use a PUT command, which requires 4 URI parameters and a Request Body. The URI parameter requirements are similar for the Virtual Network and Public IP resources.

URI Parameters – DDoS Protection:

URI Parameters – Virtual Network:

URI Parameters – Public IP:

Example of the request URI – DDoS Protection: PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/ddosProtectionPlans/{ddosProtectionPlanName}?api-version=2024-01-01 

Example of the request URI – Virtual Network: PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/virtualNetworks/{virtualNetworkName}?api-version=2024-01-01 

Example of the request URI – Public IP: PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/publicIPAddresses/{publicIpAddressName}?api-version=2024-01-01  

Request Body – DDoS Protection:

Request Body – Virtual Network:

Request Body – Public IP:

When sending a GET request or a DELETE request, we no longer require the request body, only the URI parameters to pull the information for the resource we want.

Creating an Azure DDoS Protection Plan

Azure DDoS Protection, combined with application design best practices, provides enhanced DDoS mitigation features to defend against DDoS attacks. It’s automatically tuned to help protect your specific Azure resources in a virtual network. Protection is simple to enable on any new or existing virtual network, and it requires no application or resource changes.

Creating an Azure DDoS Protection plan is incredibly simple with the API as it only accepts two definitions in the request body with only one being required, the location. Looking at the JSON example below, we’ve only defined our location for the plan to live in South Central US. The location for an Azure DDoS Protection plan is nothing more than a placeholder, as a plan can span across resource groups, subscriptions, and regions.

{

    “location”: “SouthCentralUS”

}

After sending the PUT command to create the Azure DDoS Protection plan, we’ll use a GET to pull the resource and check out what’s been created. It’s important to check the provisioning state and ensure that it is in a Succeeded state before sending another PUT. Sending another PUT while the policy is updating will place the resource into a failed state. As best practice, always check the provisioning state of all your resources before making any changes.

Using the example below, we can see the name that was passed through the URI parameters and our location that was passed in the body. You’ll also notice that there are Azure Tags associated with the protection plan. Although we didn’t set these tags in our request body, there is automation on this subscription that applies tags once created. A GET command is a great way to look at any resource in Azure and understand how that resource has been configured and its current provisioned state.

With this simple example, we can already see how REST API is a flexible and quick way to create and manage resources in Azure. This method allows us to see exactly how a resource is configured in JSON, without having to navigate multiple blades in the Azure Portal.

Protecting an Azure Virtual Network with Azure DDoS Protection

Now that we have established an Azure DDoS Protection plan, the next step is to link or associate the Azure Virtual Networks with the plan to initiate protection. First, we’ll run a GET against the virtual network to check the current protection status and if there are any plans already associated with the network. The screenshot below shows that the virtual network is not protected with Azure DDoS Protection and has no plan associated.

There is also another REST API call that can be made to check the DDoS protection status of a virtual network. The call is named ‘List Ddos Protection Status’ and we can see what this looks like below. It requires a POST call, rather than a GET, and this call might return a 202 Accepted status. This is a status code for asynchronous operations and will require a second REST API call to get the details you’re looking for. To do this in Postman, click on the Headers tab for the response and find the Header called Location. Copy the entire value that you find in the Location header and run a GET against it. If you don’t have a plan associated with the virtual network, what you’ll see is a list of Public IPs that are associated with the virtual network and if the workload is protected. Once we associate the plan we created earlier, we’ll run this call again and see how the information changes.

To get the plan associated with the virtual network, we’ll need to send an Update to Azure Resource Manager (ARM) using a PUT command, and we’ll have to be careful not to overwrite the configurations of the already existing virtual network. The best way to do this is to run a GET against the virtual network like we did earlier, then copy & paste the JSON response body into the request body of our PUT call. Once we have our already existing virtual network configurations defined in our PUT, we can then add additional body definitions to protect the virtual network with the Azure DDoS Protection plan.

Below is a JSON snippet of what this will look like. Under properties, we will change the boolean of ‘enableDdosProtection’ from false to true and then add the resourceID of the Azure DDoS Protection plan.

“enableDdosProtection”: true,

“ddosProtectionPlan”: {

    “id”: “/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/xxxxxxxx/providers/Microsoft.Network/ddosProtectionPlans/ddosPlan-restAPI”

}

We’ve associated the plan and enabled DDoS protection for the virtual network. Let’s run the ‘List Ddos Protection Status’ call once more to see what the results are. Our public IP now shows that it is a protected workload, and we can see the resourceID of the Azure DDoS Protection plan.

Lastly, let’s run a GET against our Azure DDoS Protection plan API to see if any properties have changed after associating an Azure Virtual Network. We can see below that a virtualNetworks array block has been added to the properties, with our virtual network information. This is a quick and easy way to check on all of the virtual networks associated with an Azure DDoS Protection plan.

Protecting an Azure Public IP with Azure DDoS Protection

Azure Public IP resources can be safeguarded against DDoS attacks using either Azure DDoS Network Protection or Azure DDoS IP Protection. Azure DDoS Network Protection provides comprehensive defense for entire virtual networks, leveraging always-on traffic monitoring and adaptive tuning to mitigate large-scale attacks. It requires customers to create a DDoS plan upfront which may be an overkill for SMB customers who have a small number of public IPs that they want to safeguard against DDoS attacks. For such cases, customers have an option to enable Azure DDoS IP Protection on their public IPs directly using the DdosSettings protectionMode property as shown below. Azure DDoS IP Protection offers targeted protection for individual public IP addresses. In this section, we’ll cover what it looks like when a public IP resource is protected under Azure DDoS Network Protection and how to enable Azure DDoS IP Protection.

Our first example shows a simple GET against a public IP resource that is associated with an Application Gateway in my virtual network. From the API call, we see there are ddosSettings under the properties and the protectionMode says ‘VirtualNetworkInherited’. This doesn’t truly show us the protection status of the public IP resource though, since a virtual network could be or could not be protected with a DDoS protection plan. To obtain the true value of the protection status, we’ll use another API call called ‘Ddos Protection Status’.

The ‘Ddos Protection Status’ API call is like the ‘List Ddos Protection Status’ for Azure Virtual Networks. When you make the initial POST call, you will most likely receive a 202 Accepted response. Remember to open the Headers tab in the response and copy the entire value of the Location header to run a GET call against it.

Below is a screenshot of what that call will return. We’re able to the resourceID of the public IP address, that the IP is a protected workload, and we can reference the DDoS protection plan resourceID.

To enable the Azure DDoS IP Protection SKU for an Azure Public IP resource, you would make a simple change to the ddosSettings block under properties from ‘VirtualNetworkInherited’, to ‘Enabled’. The ‘VirtualNetworkInherited’ value is the default value you’ll see on any Azure Public IP resource that has not been explicitly configured with Azure DDoS IP Protection or with a value of ‘Disabled’.

Below is a JSON snip of how to make the change with screenshot.

“ddosSettings”: {

    “protectionMode”: “Enabled”

 }

Deleting an Azure DDoS Protection Plan

Deleting an Azure DDoS Protection plan is simple but may require multiple steps if there are virtual networks associated with the plan during deletion. It is a prerequisite that all virtual network associations with the DDoS protection plan be removed before attempting a delete against the plan resource. As you can see below, I received a 400 Bad Request because there was still a virtual network that was using the DDoS protection plan. The error returned is useful, since it shows me exactly which resources are still using the plan, allowing me to go directly to that virtual network to remove the association.

Now we’ll remove the DDoS protection plan association using a PUT against the Azure Virtual Network. The removal requires that the boolean for ‘enableDdosProtection’ be set to false, and the ‘ddosProtectionPlan’ block be completely removed. Remember that since we’re only doing an Update to the virtual network resource, make sure to copy and paste a recent GET of the virtual network resource and make the minor changes to that JSON body.

Once the process above is complete, we can send the DELETE API call for the Azure DDoS Protection plan. You’ll notice that we get a 202 Accepted code and nothing in the response body. This is an indication of another async call that will require a second API call to get the information. The difference between this async call and the ones we executed previously is that we’re going to look for another Header other than ‘Location’. For our second API call, we need to find the Header, AzureAsyncOperation. Copy the full value of the AzureAsyncOperation header and run a GET against it. You’ll see a Suceeded status of the deletion for the Azure DDoS Protection plan.

Conclusion

In this guide, we’ve learned how to use the Azure REST API to create and configure an Azure DDoS Protection plan, as well as configure Azure DDoS IP Protection for a single public IP resource. We have seen how to use Postman to send HTTP requests to the Azure Resource Manager endpoint and how to authenticate with Azure Entra ID. We have also explored how to verify DDoS protection status for Azure Virtual Networks and Azure Public IP resources. To learn more about Azure REST API and Azure DDoS Protection, check out the referenced documentation below.

References

Postman API Platform | Sign Up for Free
Azure REST API reference documentation | Microsoft Learn
Status of asynchronous operations – Azure Resource Manager | Microsoft Learn
Azure DDoS Protection Overview | Microsoft Learn
Ddos Protection Plans – REST API (Azure Virtual Networks) | Microsoft Learn
Virtual Networks – REST API (Azure Virtual Networks) | Microsoft Learn
Public IP Addresses – REST API (Azure Virtual Networks) | Microsoft Learn

​Microsoft Tech Community – Latest Blogs –Read More 

Hi,

I am working on upgrading a server from 2012 to 2022 (on AWS). I have installed a fresh 2022 instance and have sued webdeploy to copy the entire IIS configuration from the 2012 server to the 2022 server.

To try to further bring the server up to date, the 2012 server is running .Net 2.x and on 2022 I have installed .Net 8.x

When I launch the 2022 server IIS runs but my websites won’t come up – I keep getting a 503 error. When I look in the Event Viewer the error message I see is “apsnetcore.dll not found”. I have spent some time trying to identify how to rectify this but so far have not been successful. Could anyone please give me any suggestions to try to find a fix ?

TIA

​Hi, I am working on upgrading a server from 2012 to 2022 (on AWS). I have installed a fresh 2022 instance and have sued webdeploy to copy the entire IIS configuration from the 2012 server to the 2022 server. To try to further bring the server up to date, the 2012 server is running .Net 2.x and on 2022 I have installed .Net 8.x When I launch the 2022 server IIS runs but my websites won’t come up – I keep getting a 503 error. When I look in the Event Viewer the error message I see is “apsnetcore.dll not found”. I have spent some time trying to identify how to rectify this but so far have not been successful. Could anyone please give me any suggestions to try to find a fix ?TIA  Read More

​

How can I increase the distance between the automatic numbering and the chapter name in Styles in Word so that there is enough space between, for example, 1000. and the Chapter name for a neat image.

​How can I increase the distance between the automatic numbering and the chapter name in Styles in Word so that there is enough space between, for example, 1000. and the Chapter name for a neat image.  Read More

​

A while ago there was a change that the SharePoint invitation manager has been converted to the Entra invitation manager.

This is a good thing because every guest can use the OTP for logging in.

Only I see this behaviour:
When a guest has been added to a group or a team. The guest can sign in with OTP to the team. Also there is a guest account created.

When I share a folder or a document the guest can sign in with the OTP to the folder or document. But there is no guest account in M365 for this user. So you don’t have an overview of the guest accounts in your tennant where a document has been shared with.

With Powershell you can edit the entra invitation manager a bit:

Set-SPOTenant -EnableAzureADB2BIntegration $true

After completing this command also the users when you share something will be addeAuthenticationd as a guest.

Is it default that guests are not vissible when you share a folder or document with them? Is this the right approuch to get a view of those accounts?

Maurits Knoppert

​A while ago there was a change that the SharePoint invitation manager has been converted to the Entra invitation manager. This is a good thing because every guest can use the OTP for logging in.Only I see this behaviour:When a guest has been added to a group or a team. The guest can sign in with OTP to the team. Also there is a guest account created. When I share a folder or a document the guest can sign in with the OTP to the folder or document. But there is no guest account in M365 for this user. So you don’t have an overview of the guest accounts in your tennant where a document has been shared with. With Powershell you can edit the entra invitation manager a bit:Set-SPOTenant -EnableAzureADB2BIntegration $true After completing this command also the users when you share something will be addeAuthenticationd as a guest. Is it default that guests are not vissible when you share a folder or document with them? Is this the right approuch to get a view of those accounts? Maurits Knoppert  Read More

​

When you click on “Expand background” the description returned is for incorrect image.

So, for my browser today the image of Arizonan Saguaro the description is “Tawny frogmouth chick, Australia”. This seems to occur with any image.

​When you click on “Expand background” the description returned is for incorrect image.So, for my browser today the image of Arizonan Saguaro the description is “Tawny frogmouth chick, Australia”. This seems to occur with any image.  Read More

​

As we were building the Copilot learning hub on Microsoft Learn earlier this year, I realized how much Copilot was changing the way so many people—from my 78-year-old father to my teammates—complete daily tasks. I had first-hand insight into how, as an AI companion, Copilot enables us to be more creative and more efficient across a broad range of activities.

When Microsoft released Copilot in March 2023, our customers had questions. They wanted to know how they could use Copilot to be more productive at work and in their personal lives. They were curious how to use Copilot within Microsoft 365 applications, like Word, PowerPoint, Outlook, and Teams, and how to leverage Copilot for developers, data scientists, and security professionals.

To answer these questions and more, we created the Copilot learning hub in May 2024. I recently asked Dona Sarkar and Dan Wahlin, Microsoft Principal Cloud Advocates—and members of the learning hub team—to share some of their stories about creating this powerful resource.

The Copilot learning hub is “designed to meet learners wherever they are along their learning and adoption journey,” said Dona, “from understanding and using copilots, to customizing them with their own data, and, finally, building their own copilot.” The learning hub caters to technical audiences and ensures that each learner accesses content that is tailored to their learning goals. These resources augment the content available on the AI learning hub, which is designed for both technical and non-technical learners.

These goals are grouped into four task-based Microsoft Learn Official Collections—understand, adopt, extend, and build – providing content specific to each stage of the learning journey. Each collection contains a variety of training modules, documentation, and videos. Learners can even access content that is applicable to specific tech roles, such as administrators, data analysts, and developers.

One learner favorite on the hub is the video library, which provides Copilot instructional content and customer use cases. According to Dan Wahlin: “People love to see what’s possible and the benefits from using a copilot, so our videos focus on that angle. We show how a copilot makes both personal and work life easier and more productive, how creativity is enhanced, and how people can get started and immediately experience these benefits themselves.”

Dona adds that the videos demonstrate the diverse applications of Copilot across Microsoft products and services. “People share their favorite Copilot use cases and how they leverage Copilot in various scenarios,” she said. “This approach makes the content more relatable and engaging by featuring stories from a wide range of professionals.”

Check out this video to learn how cultural shifts and human factors play a crucial role in the successful implementation of AI technology like Copilot.

Check out this video to learn how cultural shifts and human factors play a crucial role in the successful implementation of AI technology like Copilot. 

Dona shared her own story about how learning a new programming language has changed now that she can rely on Copilot to assist her with her learning. Recently, she used GitHub Copilot as a coding coach to learn Python after working in C# for 20 years. Dona recalls it took her a full year to learn JavaScript years ago, but only one month to learn Python using Copilot. “That’s a real game changer. Imagine how Copilot can help expert and novice programmers alike gain new skills and do their jobs better,” she said. This is the true promise of the Copilot learning hub—putting expert content to work for you so you can excel using Copilot.

With all the excitement around Copilot, we continue to provide new resources for learners. “We’ve received great feedback on the Copilot learning hub from learners. They’ve expressed how they appreciate the comprehensive resources and real-world examples available,” Dan said. “They’ve also provided us with great feedback that we’re consistently applying to continue to take the Copilot learning hub to the next level.”

Erica Woods, Director of Contractor Programs & Philanthropy and Principal at Apex Systems in Tampa, FL, has completed several modules and videos showcased on the learning hub. “I appreciate several things in the Copilot learning hub,” Erica said, “including insights on different ways to apply the technology that are easy to build directly into my day-to-day, the bite-sized chunks the training segments are delivered in, demo-style learning, the fun and conversational style of the videos, and the variety of topics included.” 

So, what’s next? These are some new resources you can expect to see in the coming months, each designed to further streamline your workflow and enhance your Copilot experience:

In the weeks leading up to Microsoft Ignite, you’ll see new content on the “agentification” of Copilot. What are agents? They are copilots that can act independently, triggered by events—not just conversation—enabling you to automate and orchestrate complex, long-running business processes with less human intervention. For example, an “order taker” copilot can handle the end-to-end order fulfillment process—from taking the order, to processing the order and making intelligent recommendations and substitutions for out-of-stock items, to shipping to the customer.
We are also working on stories showcasing how Microsoft customers and partners are helping their customers use Copilot, particularly in specialized industries like finance, manufacturing, and others.

Coming up: In our next Get AI ready blog, discover how Microsoft Training Services Partners (TSPs) are helping organizations worldwide build AI skills and stay competitive. Learn about the benefits of AI-powered tools and services, and how TSPs provide customized training plans to ensure your teams are AI-ready. Read inspiring stories from Sulava, Skillsoft, and Koenig Solutions, and find out how they are transforming businesses with AI. Don’t miss out on this opportunity to upskill your workforce and drive innovation.

​Microsoft Tech Community – Latest Blogs –Read More 

Attention security professionals! Microsoft Ignite 2024 is just around the corner, taking place from Monday, November 18, 2024, through Friday, November 22, 2024, in Chicago, Illinois. This is your chance to dive deep into the latest advancements in AI and security to help you build a security-first culture within your organization. 

General in-person passes are sold out, but don’t worry—you can still purchase a pass using Microsoft Security’s RSVP code. Use the RSVP code ATTNLIYL to purchase your in-person pass while supplies last. 

Why attend?

For security professionals and teams, AI offers a significant advantage, empowering organizations of all sizes and industries to tip the scales in favor of defenders. It also introduces new uncertainties and risks that require organizations to create a culture of security to stay protected. Now, more than ever, is the time to put security first. But how? 

The answer is: with our innovations in AI-first, end-to-end security. 

Ignite is our opportunity to share and showcase our latest security product innovations with you, and then dive into the technical details together—so the information you learn at Microsoft Ignite can have an immediate benefit to your digital environments and your customers. 

Here’s what you can expect: 

See your favorite products in action during sessions, demos, interactive labs, and workshops. 

Learn how our global-scale threat intelligence informs the products you use daily. 

Gain AI-specific cybersecurity skills to make you an invaluable asset to your organization.  

Engage with Microsoft security product innovators and thought leaders. 

Network with fellow security leaders, partners, and technical enthusiasts. 

Microsoft Security at Microsoft Ignite: An expanded experience 

Last year, you asked for more security content, we delivered—and we received great feedback. So this year we’re planning even more, with a focus on our continuing commitment to securing our technology and our customers. 

See an overview of the week below to plan your travel. 

Day 0 November 18, 2024 

Microsoft Ignite Security Forum 

Join us one day early at Microsoft Ignite for a security-only program, designed for decision makers from businesses of all sizes. Learn how AI, threat intelligence, and insights from our Secure Future Initiative can advance your security strategy. Be sure to sign up for this experience in registration. 

Pre-day Labs Sessions 

We’re also offering two technical pre-day learning labs: 

1. “Secure your data estate for a Copilot for M365 deployment”: In this lecture-based workshop, Microsoft experts will walk you through a best practice, staged approach to securing your data estate ready for Copilot and other AI tools. 

2. “AI Red Teaming in Practice”: This pre-day hands on workshop, led by Microsoft AI Red Team experts, is equipped to probe any machine learning system for vulnerabilities, including prompt injection attacks. 

Day 1 November 19, 2024 

Keynote  

Satya Nadella said in May that security is job #1. Don’t miss the live keynote for the latest security innovations impacting Microsoft. 

Security General Session 

Microsoft Security’s top engineering and business leaders will share an overview of how our most exciting innovations help you put security first and best position your organization in the age of AI.  

Security programming  

Dive deeper into topics that interest you. Choose from over 30 breakout sessions, demos, and discussions covering end-to-end protection, tools to secure and govern AI, responsible AI, and threat intelligence.  

Day 2 November 20, 2024 

Security programming  

Dive deeper into topics that interest you. Choose from over 30 breakout sessions, demos, and discussions covering end-to-end protection, tools to secure and govern AI, responsible AI, and threat intelligence.  

Secure the Night Party 

Security is often a thankless job. If no one else celebrates you, Microsoft Security will! Join us for a special party for the cybersecurity community.  

Day 3 November 21, 2024 

Security programming  

Dive deeper into topics that interest you. Choose from over 30 breakout sessions, demos, and discussions covering end-to-end protection, tools to secure and govern AI, responsible AI, and threat intelligence.  

Closing Microsoft Ignite Celebration  

Close out Microsoft Ignite with the other 10,000+ attendees across job functions, industries and the world.  

Don’t miss this opportunity to elevate your security strategy and stay ahead of evolving cyber threats. Plan your travel now and be part of this transformative event! Use the RSVP code ATTNLIYL to purchase your in-person pass while supplies last. 

​Microsoft Tech Community – Latest Blogs –Read More 

Today we are announcing that the Cloud Policy service is now available to Microsoft 365 Government Cloud customers.

The Cloud Policy service allows Microsoft 365 administrators to configure policies for Microsoft 365 Apps for enterprise and assign these policies using Microsoft 365 groups or Entra ID groups.  Once configured, these policies are automatically enforced as users sign in and use Microsoft 365 apps.

The initial release will support policies for Microsoft 365 Apps for enterprise on Windows and future updates will bring support for additional applications and platforms.

For additional information about the Cloud Policy service, refer to Overview of the Cloud Policy service for Microsoft 365 Apps for enterprise.

Microsoft 365 roadmap https://www.microsoft.com/en-us/microsoft-365/roadmap?rtc=2&filters=GCC&searchterms=393925

_____________________________________________________________________________________________

Continue the conversation by joining us in the Public Sector Tech Community Whether you have product questions or just want to stay informed with the latest updates on new releases, tools, and blogs, our Community is your go-to resource to stay connected!

​Microsoft Tech Community – Latest Blogs –Read More