No support for Protected Users in Microsoft Entra Domain Services?
I have been loooking into mapping best practices about configuring hardening / tiering model from on-premises Active Directory to Microsoft Entra Domain Services (MEDS). I'm well aware that MEDS is NOT a replacemenet for AD DS and have many restrictions and missing features, but that does not stop me from wanting to make it as secure as possible for member servers to be joined to. Since MEDS is a PaaS in Azure, deployed from within Azure and managed in another way than Active Directory, of course there are different ways of implementering a good tiering model. In my study I wanted to see if I could enable Protected Users feature (join users to Protected Users Group). However I find this group to be present but not possible to add members to (feature greyed out). I have a member server in the MEDS instance and have installed AD DS Tools. My user is member of AD DDS Administrators group. I would like to know if anyone have some knowledge on the subject to share?
How to Optimize your Codespaces: Pro-tips for managing quotas
Now that GitHub Codespaces is free for anyone, you might be surprised to see how fast you can hit the free quota. Here are four things you can do to make the most out of the 90 hours you get every month (and 180 hours if you are a student).
Proactive private share #microsoft
Many comapanies is part of my job last two year. I desade to implement and create new public communty group at microsoft, with public share. Like universal patch insade giant org and partner companes ,microsoft deside lead postiton. Proacticve and future plan is constructed to grow on world network with client and our partnersA Complete Guide to Azure Cost Management
As companies shift to the cloud, managing the costs is as important as using the cloud to its fullest. Azure is one of the most popular cloud platforms, and it offers a lot of benefits such as scalability and flexibility; however, if you do not manage the costs associated with the cloud, you are likely to spend a lot of money. This is where Azure Cost Management comes in to help you get the most out of your cloud spending and how to use the money you spend on cloud services wisely. What is Azure Cost Management? Azure Cost Management is a set of tools available within the Azure platform that helps organizations in managing the costs of their cloud resources, optimizing their usage and sticking to the budget. It is integrated with Azure services to help in identifying waste and ways of getting the most out of the investment. Key Features of Azure Cost Management Cost Analysis Azure Cost Analysis gives you a clear view of your expenditure and helps you identify where your money is going. You are also able to customize your views to the resources, subscriptions, services or the regions to notice the changes and exceptions. Budgets Establish your funds with budgets to ensure that you do not spend more than you had intended to on Azure. Azure allows you to create budgets for certain subscriptions, resource groups or even services and it will send you notifications when you are about to reach or even go beyond your limits. This is a proactive way that prevents you from incurring exceeding charges. Cost Allocation with Tags Azure supports the concept of tagging, which means that you can associate keys (such as department, project, or environment) with resources. These tags are useful in helping assign the costs to the right teams or objects for example departments or projects. Suggestions for Enhancement Azure Cost Management is integrated with Azure Advisor to offer suggestions that include downsizing underutilized VMs, purchasing reserved instances, or identifying inactive resources. Integration with Power BI For more sophisticated reporting, Azure Cost Management is integrated with Power BI, which allows you to design your own reports and dashboards that meet your company’s requirements. Multi Cloud Support Azure Cost Management is not only limited to Azure, it also includes AWS thereby enabling organizations with a multi-cloud strategy to manage the costs of all the clouds from one platform. Tips for the Effective Implementation of Azure Cost Management: To enhance the usage of Azure Cost Management, implement the following tips: Implement Cost Governance Establish roles and responsibilities to ensure that spending is appropriate. Use Azure Policy to set policies such as restricting the creation of high-cost resources in some subscriptions. Monitor Spending Regularly Set up some alerts and review the spending reports frequently. This way you can notice any irregularities and deal with them before they become a problem. Use Reserved Instances and Savings Plans For the workloads with the certain schedule, it is recommended to buy Azure Reserved Instances or Azure Savings Plans that provide a significant price reduction compared to the pay as you go pricing. Optimize Resource Usage Shut down or remove inactive resources, shrink VMs to the required size, and use scaling to vary the resources according to the need. Leverage Spot VMs For less critical or lightweight tasks that can tolerate some level of downtime, Azure Spot VMs can be used to reduce the overall cloud spending. Tag and Organize Resources It is important to have a good tagging practice in place to increase the cost visibility. Some of the tags could be Project: AI Research, Department: Marketing and so on that help in identifying the costs and managing the spend against the right projects and departments. Real World Benefits of Azure Cost Management Example 1: Optimization for Reducing Costs A SaaS company was able to decrease its cloud spending by 30% by identifying dormant resources and downsizing over provisioned VMs with the help of Azure Cost Management suggestions. Example 2: Improved Budgetary Control An enterprise IT department did not spend more than the budget because it established subscription-level budgets and received notifications when the consumption was close to the limits. Example 3: Multi Cloud Efficiency A global company combined the tracking of its cloud expenses across Azure and AWS using Azure Cost Management and was able to generate one unified report for all the clouds, which in turn helped it make better financial decisions. The Future of Cost Management in Azure As cloud environments become more sophisticated, cost management tools will keep on developing. Some of the other features that are expected to be incorporated in the future include the use of artificial intelligence in the generation of insights, prediction, and better integration with DevOps processes. Thus, using Azure Cost Management, organizations can graduate from the reactive spending control to the proactive cost optimization and thus make sure that their cloud journey is not only creative but also economic. Sum up Azure Cost Management is a valuable tool for anyone seeking to manage, minimize, and explain cloud expenditure. Whether you are a small business or a large enterprise, these tools help you make decisions based on data, increase your ROI, and gain financial visibility in the cloud. Get started with Azure Cost Management today, and discover how to maximize your cloud spend while maintaining a healthy budget.[server 25314] External SET Team to Internal after Reboot.
I have created SET Teaming on Windows Server 25314 (actually from a previous build) using External and 3 Intel i350-T4 ports, configured for Hyper-V and external access. New-VMSwitch -Name SETSwitch -NetAdapterName "i350t4_1","i350t4_2","i350t4_3" -AllowManagementOS $true -EnableEmbeddedTeaming $true -EnableIov $true Set-VMSwitchTeam -Name SETSwitch -LoadBalancingAlgorithm Dynamic In that case, the Hyper-V VM and OS can be accessed normally, but when I restart Windows Server, all Adapters disappear from SET Teaming and are changed to the Internal setting, and network access is lost. The above logs were obtained at WPR with Profile in Network. Since the file is large, I will post a link to OneDrive. setTeamingTrouble.etl https://1drv.ms/u/s!AoGvAA_XXMTH-dJ2gkOa6E5hP4QhLg?e=7hPgLQ In addition, if the EnableIov option is set to $false, a BSOD (KMODE_EXCEPTION_HANDLED) will occur after the Switch is created. VMSWITCH.SYS 0x0000007e (0xffffffffc0000005, 0xfffff80643a95c61, 0xffffb28989f2a6d8, 0xffffb28989f29ef0) Addition 2: LBFO Teaming is working properly. I tried to send it through the Feedback Hub and could not get it to work, so I have included it here. Addition 3: Server 25324 LBFO Teaming with New-VMSwitch failed.
BPA Errors: DNS can't resolve GC, Kerberos, PDC Resource Record, etc.
Hello, I've been poking around this for hours now and could use another set of eyes. This server has been the PDC for quite some time but I discovered the last people that managed this place, didn't demote the old 2008R2 server (thankfully it still existed virtualized). So I was able to do a graceful demotion of that and removed it from the domain. I'm now trying to resolve some other errors in that come up in the BPA scan... All reference DNS and I just can't figure this out. I've been beating head against the wall trying to understand what's happening, This is MS Server Standard 2022 only 1 DC and DNS. (yeah I know, don't get me started, but it's a really small office)... Would love some suggestions. Thanks!Log Analytics Agent-based Azure Management Services: Shut down starting 28 February 2025
Overview The legacy Log Analytics (LA) agent, which has played a critical role in transferring data logs for software and applications to Azure, was deprecated on August 31, 2024. Subsequently, all Azure services and solutions relying on the Log Analytics agent for data collection are also being phased out. This transition ensures a seamless shift to more robust replacement products, enhancing continuity, security, and performance for customers' IT estates. Two of the Azure Automation solutions provided management of machines using the LA agent namely, Azure Automation Update Management for streamline software update deployment & Azure Change Tracking & Inventory for tracking changes and inventory for in-guest environments. These agent-based services were also deprecated on 31 st August 2024. Over the last 6 months, these solutions were maintained, giving customers time to move their management processes to the replacement products. In order to ensure a security posture of the customer environments, these LA agent-based solutions will be completely shut down starting 28 th February 2025. You may encounter your existing patching jobs fail and staleness in the changes data in the log analytics workspace after this date. Following captures further details on the impact to operations for the machines that continue to be on these solutions and provides additional guidance. What will change after 28 th February 2025? a) You will not be able to access both Azure Automation Update Management & Azure Change Tracking & Inventory enabled with the LA agent from the Azure Portal. b) For Azure Automation Update Management, no new periodic assessments or patching data corresponding to configured machines will be populated. c) For Change Tracking & Inventory with LA agent, no new changes or inventory logs will be captured. Note: Historical data for the last 30 days will continue to be available in LA workspace and can be directly queried from the LA tables LA workspace table Purpose ConfigurationData To obtain inventory logs for auditing and compliance needs ConfigurationChange To obtain logs corresponding to the changes made in customer environment Update To query periodic assessments and patched updates data for pending updates view What next? If you have any machines configured with legacy version of above-mentioned services, please use one of the following available methods to migrate to replacements products – Product Service Product Migration Guidance Azure Change Tracking & Inventory with LA agent a) Migrate to Azure Monitoring Agent (AMA) version of Change Tracking & Inventory – Using Azure Portal Using PowerShell b) If you have enabled File Integrity monitoring (FIM) with LA agent & managing it via Change Tracking & Inventory experience, here are the available options to migrate to - Move to Change Tracking & Inventory with AMAfor enhanced insights for data types including Files, Registry Keys, Software, Windows Services, Linux Daemons, File content changes. Move to FIM with MDE (part of Defender for Servers Plan 2) Azure Automation Update Management Migrate to Azure Update Manager (Does not rely on AMA) Using Azure Portal Using Runbook scripts Additionally, you can refer to these instructions to disable LA agent from your environment. Please feel free to reach out to us on aumpm@microsoft.com for any queries or feedback.
ACPI/INTC1085 driver is not installed
Hello. I have a server platform ASUS RS300-E12-RS4 with Intel(R) Xeon(R) E E-2478. After installation microsoft hyper-v server 2019 and install all drivers from asus site, i have 1 not installed device. ACPI\INTC1085\2&DABA3FF&1 driver "INTEL_Serial_IO_V30.100.2237.26.zip" not compatible for this device. BIOS version is 0803 BMC version is 1.0.9 The support of the hardware manufacturer could not help me, they recommended to contact the OS manufacturer.M365 Management
Hi all, Cards on the table—I’m a Product Manager for a solution focused on Microsoft 365 management as well as driving optimisation into innovation. My background is sysadmin-heavy, which led me to building the solution before moving into product. I’m not here to pitch anything but genuinely keen to hear from the community: What are your biggest pain points in managing M365, Azure, Copilot? What challenges do you face with user optimisation, processes etc? Are you using any tools today to help, or is it mostly manual? What is one thing that would make your life so much easier? Would love to hear what’s working (or not working) for you, as it would help me massively! Thanks!
