<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure AD</title><link>https://evotec.xyz/de/categories/azure-ad</link><description>Evotec Main Website</description><atom:link href="https://evotec.xyz/de/categories/azure-ad/index.xml" rel="self" type="application/rss+xml" /><item><title>Upgrade Azure Active Directory Connect fails with unexpected error</title><link>https://evotec.xyz/de/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error</link><description>Today, I made the decision to upgrade my test environment and update the version of Azure AD Connect to the latest one. The process is usually simple: download a new MSI, run it, click next a few times, enter the credentials for your Global Admin, and you’re finished. However, this time, I encountered an error.</description><pubDate>Wed, 02 Oct 2024 12:17:34 GMT</pubDate><guid>https://evotec.xyz/de/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error</guid><category>azure ad</category><category>azure adconnect</category><category>error</category><category>errors</category><category>Office 365</category><category>office365</category></item><item><title>Active Directory Health Check using Microsoft Entra Connect Health Service</title><link>https://evotec.xyz/de/blog/active-directory-health-check-using-microsoft-entra-connect-health-service</link><description>Active Directory (AD) is crucial in managing identities and resources within an organization. Ensuring its health is pivotal for the seamless operation of various services. Today, I decided to look at Microsoft Entra Connect Health (Azure AD Connect Health) service, which allows monitoring Azure AD Connect, ADFS, and Active Directory. This means that under a single umbrella, you can have an overview of three services health. But is it worth it?</description><pubDate>Sun, 08 Oct 2023 14:36:57 GMT</pubDate><guid>https://evotec.xyz/de/blog/active-directory-health-check-using-microsoft-entra-connect-health-service</guid><category>Active Directory</category><category>Azure</category><category>azure ad</category><category>health checks</category><category>microsoft entra</category><category>powershell</category></item><item><title>Report Active Directory Accounts that are Synchronized with Azure AD</title><link>https://evotec.xyz/de/blog/report-active-directory-accounts-that-are-synchronized-with-azure-ad</link><description>I was scrolling X (aka Twitter) today and saw this blog post, “PowerShell: Report On-Premises Active Directory Accounts that are Synchronized with Azure AD Connect” by Kevin Trent. I like reading blog posts as I tend to learn some new things and see how people tend to solve their problems.</description><pubDate>Mon, 07 Aug 2023 13:21:18 GMT</pubDate><guid>https://evotec.xyz/de/blog/report-active-directory-accounts-that-are-synchronized-with-azure-ad</guid><category>active directory</category><category>ad</category><category>azure ad</category><category>microsoft graph</category><category>powershell</category></item><item><title>Upload and Download files from Azure Blob Storage using Connection String</title><link>https://evotec.xyz/de/blog/upload-and-download-files-from-azure-blob-storage-using-connection-string</link><description>They say there is a first time for everything. For me, it’s how to download and upload files to Azure Blog Storage using Connection String. Recently I was given Connection String, Container name and had to download some files from Azur Blog Storage. After some research and trying Connect-AzAccount, I found that the proper way to go is thru New-AzStorageContext.</description><pubDate>Wed, 18 Jan 2023 19:13:24 GMT</pubDate><guid>https://evotec.xyz/de/blog/upload-and-download-files-from-azure-blob-storage-using-connection-string</guid><category>az.storage</category><category>azure ad</category><category>azure blob storage</category><category>download</category><category>powershell</category><category>upload</category></item><item><title>Mentioning users in notifications using PSTeams PowerShell Module</title><link>https://evotec.xyz/de/blog/mentioning-users-in-notifications-using-psteams-powershell-module</link><description>Microsoft Teams over the last few years have grown into an excellent and flexible tool for both small and big companies. Having the ability to chat with users, store files or have all sorts of data in one place makes it easy and functional. Of course, it has its fair share of issues, but it’s getting better. One of the cool features of Microsoft Teams is being able to send notifications to Microsoft Teams Channels using WebHook Notifications. In the beginning, this feature was pretty limited, but after a few years, it got much better with support for Adaptive Cards, List Cards, Hero Cards, Thumbnail Cards, and Office 365 Connector Card.</description><pubDate>Sun, 16 Jan 2022 19:08:52 GMT</pubDate><guid>https://evotec.xyz/de/blog/mentioning-users-in-notifications-using-psteams-powershell-module</guid><category>Azure AD</category><category>microsoft teams</category><category>office 365</category><category>powershell</category><category>psteams</category></item><item><title>Configuring Office 365 settings using PowerShell – The non-supported way</title><link>https://evotec.xyz/de/blog/configuring-office-365-settings-using-powershell-the-non-supported-way</link><description>Office 365 is a huge beast. It has so many services that it’s hard to track all of them. It’s even harder if you want to manage Office 365 using PowerShell. Microsoft makes many different PowerShell modules available for you, such as AzureAD, AzureADPreview, ExchangeOnline, MicrosoftTeams, and recently, Microsoft.Graph. But even with so many different modules, there are still tasks that Microsoft won’t let you do from PowerShell. But it doesn’t mean that it’s not possible to do it. I’ve spent some time tracking how Microsoft does things while you click thru the interface and created an O365Essentials PowerShell module that can do it in an automated way.</description><pubDate>Sun, 26 Sep 2021 15:12:35 GMT</pubDate><guid>https://evotec.xyz/de/blog/configuring-office-365-settings-using-powershell-the-non-supported-way</guid><category>Azure</category><category>Azure AD</category><category>graph api</category><category>microsoft graph</category><category>microsoft office 365</category><category>module</category><category>o365essentials</category><category>office 365</category><category>powershell</category><category>powershellgallery</category></item><item><title>Mailozaurr – New mail toolkit (SMTP, IMAP, POP3) with support for oAuth 2.0 and GraphApi for PowerShell</title><link>https://evotec.xyz/de/blog/mailozaurr-new-mail-toolkit-smtp-imap-pop3-with-support-for-oauth-2-0-and-graphapi-for-powershell</link><description>Today, I’m introducing a new PowerShell module called Mailozaurr. It’s a module that aims to deliver functionality around Email for multiple use cases. I’ve started it since native SMTP cmdlet Send-MailMessage is obsolete, and I thought it would be good to write a replacement that adds more features over it as things around us are changing rapidly.</description><pubDate>Tue, 04 Aug 2020 10:31:02 GMT</pubDate><guid>https://evotec.xyz/de/blog/mailozaurr-new-mail-toolkit-smtp-imap-pop3-with-support-for-oauth-2-0-and-graphapi-for-powershell</guid><category>Azure AD</category><category>imap</category><category>mailozaurr</category><category>o365</category><category>office 365</category><category>pop3</category><category>powershell</category><category>smtp</category></item><item><title>Azure AD – Removing Inactive Azure AD Pass-through Agent</title><link>https://evotec.xyz/de/blog/azure-ad-removing-inactive-azure-ad-pass-through-agent</link><description>Recently I was switching Office 365 tenant from ADFS to Azure AD Pass-through authentication (PTA). It all went smoothly with one exception. After removing one of the Azure AD Connect servers and all applications from its Azure AD Connect interface still is showing said agent, just inactive.</description><pubDate>Sat, 25 Apr 2020 18:28:30 GMT</pubDate><guid>https://evotec.xyz/de/blog/azure-ad-removing-inactive-azure-ad-pass-through-agent</guid><category>azure ad</category><category>azure adconnect</category></item><item><title>Office 365 – Limiting license to minimum apps required</title><link>https://evotec.xyz/de/blog/office-365-limiting-license-to-minimum-apps-required</link><description>Office 365 has a lot of options and applications to choose from. Enabling one E1, E3, or any other license gives the user a lot of features, including Exchange, SharePoint, and Teams. But what if you want to make sure that the user can access only Microsoft Teams? By default, you can do it manually during the assignment of the license. Simply choose only Apps you want to assign to a user.</description><pubDate>Tue, 07 Apr 2020 17:30:02 GMT</pubDate><guid>https://evotec.xyz/de/blog/office-365-limiting-license-to-minimum-apps-required</guid><category>azure ad</category><category>office 365</category><category>powershell</category></item><item><title>Office 365 – msExchHideFromAddressLists does not synchronize with Office 365</title><link>https://evotec.xyz/de/blog/office-365-msexchhidefromaddresslists-does-not-synchronize-with-office-365</link><description>In my life I’ve deployed multiple Office 365 tenants connected with Active Directory and I’ve been synchronizing msExchHideFromAddressLists field from…</description><pubDate>Tue, 24 Mar 2020 19:56:57 GMT</pubDate><guid>https://evotec.xyz/de/blog/office-365-msexchhidefromaddresslists-does-not-synchronize-with-office-365</guid><category>azure ad</category><category>msExchHideFromAddressLists</category><category>office 365</category><category>powershell</category></item><item><title>AzureAD – Enable Password Expiration with Password Hash Synchronization</title><link>https://evotec.xyz/de/blog/azuread-enable-password-expiration-with-password-hash-synchronization</link><description>Azure AD Connect allows three ways to make sure the user password is the same in Active Directory and Office 365. Those are Password Hash Sync, Pass-Thru Authentication, and ADFS. While my preferred option to go with would be Pass-Thru Authentication, only Password Hash Synchronization is the easiest and least resource-intensive. It synchronizes user password to Office 365, and even if your Active Directory is down, you can still log in to Office 365. It’s perfect for small and even more significant companies that don’t have resources or can’t guarantee that their infrastructure will stay 100% time online so users can authenticate based on their Active Directory.</description><pubDate>Mon, 24 Feb 2020 19:53:50 GMT</pubDate><guid>https://evotec.xyz/de/blog/azuread-enable-password-expiration-with-password-hash-synchronization</guid><category>Active Directory</category><category>azure ad</category><category>azure adconnect</category><category>powershell</category></item><item><title>How to find different server types in Active Directory with PowerShell</title><link>https://evotec.xyz/de/blog/how-to-find-different-server-types-in-active-directory-with-powershell</link><description>Working as a freelancer is a great thing if you can handle it. Each day, each week something new happens and a new problem shows up on my doorstep. It also means it’s almost never boring at your job and you get to play with new stuff. But there’s one drawback to this. You’re often thrown at the problem, told to fix it but often that’s about as much information as you get. It wasn’t very different today. I was told to switch Office 365 from ADFS to Password Synchronization. While reasons for this are not really important, the important question here is what is the name of AD Connect server that’s responsible for this configuration?</description><pubDate>Wed, 06 Feb 2019 18:25:30 GMT</pubDate><guid>https://evotec.xyz/de/blog/how-to-find-different-server-types-in-active-directory-with-powershell</guid><category>active directory</category><category>ad</category><category>adconnect</category><category>azure ad</category><category>exchange</category><category>Hyper-V</category><category>powershell</category><category>sql</category><category>windows</category></item><item><title>Azure AD Connect – Completed-Export-Errors – Permission-Issue</title><link>https://evotec.xyz/de/blog/azure-ad-connect-completed-export-errors-permission-issue</link><description>During synchronization of Active Directory with Office 365 via Azure AD Connect I was greeted with a list of accounts that have permission-issue. Error message by itself gives you a slight hint, but it doesn’t tell you exactly where to look.</description><pubDate>Thu, 29 Nov 2018 11:15:53 GMT</pubDate><guid>https://evotec.xyz/de/blog/azure-ad-connect-completed-export-errors-permission-issue</guid><category>azure</category><category>azure ad</category><category>windows</category></item><item><title>Azure AD Connect – Synchronizing MAIL field with UserPrincipalName in Azure</title><link>https://evotec.xyz/de/blog/azure-ad-connect-synchronizing-mail-field-with-userprincipalname-in-azure</link><description>Azure AD Connect is an application responsible for synchronizing Active Directory with Azure AD allowing for a natural population of users, groups, and devices in Office 365. While for most companies standard setup is very easy and most of the time touch-free, there are companies which require greater customization. During installation of AD Connector, you choose what should be used for Azure AD Username from your AD. UserPrincipalName field is an obvious choice for this and also proposed by default for that purpose. This field is utilized further by your users to log in to your Exchange, SharePoint, Teams and so on.</description><pubDate>Fri, 09 Nov 2018 21:45:47 GMT</pubDate><guid>https://evotec.xyz/de/blog/azure-ad-connect-synchronizing-mail-field-with-userprincipalname-in-azure</guid><category>active directory</category><category>azure</category><category>azure ad</category><category>office 365</category></item><item><title>Office 365 – The following error occurred during validation in agent Archive ParameterSet Enforcement Agent</title><link>https://evotec.xyz/de/blog/office-365-the-following-error-occurred-during-validation-in-agent-archive-parameterset-enforcement-agent</link><description>I just created 80 Azure AD users via PowerShell that I wanted to activate for email. Normally you can use Enable-Mailbox when…</description><pubDate>Wed, 26 Sep 2018 20:10:12 GMT</pubDate><guid>https://evotec.xyz/de/blog/office-365-the-following-error-occurred-during-validation-in-agent-archive-parameterset-enforcement-agent</guid><category>Azure AD</category><category>exchange online</category><category>office 365</category><category>powershell</category></item><item><title>PSWinDocumentation – Export to Word, Excel, SQL of AD, AWS, Exchange, O365 Exchange, O365 Azure AD</title><link>https://evotec.xyz/de/blog/pswindocumentation-export-to-word-excel-sql-of-ad-aws-exchange-o365-exchange-o365-azure-ad</link><description>Today I’m pushing forward with PSWinDocumentation project. I’ve fixed some bugs but I also added a couple of new features. I did lie a bit in the first sentence because this time it’s not all me. I got help from Mateusz Niemczyk who is a certified AWS engineer working for Euvic with me on some projects. If you’ve not yet guessed where I got him involved from the introduction – yes we’re adding basic AWS data support to PSWinDocumentation. But that’s not all…</description><pubDate>Sun, 23 Sep 2018 20:39:26 GMT</pubDate><guid>https://evotec.xyz/de/blog/pswindocumentation-export-to-word-excel-sql-of-ad-aws-exchange-o365-exchange-o365-azure-ad</guid><category>Active Directory</category><category>aws</category><category>Azure AD</category><category>excel</category><category>exchange</category><category>export</category><category>office 365</category><category>powershell</category><category>pswriteexcel</category><category>PSWriteWord</category><category>sql</category><category>Windows</category><category>word</category></item><item><title>CollectGuestLogs.exe – High Disk Usage on Azure VM</title><link>https://evotec.xyz/de/blog/collectguestlogs-exe-high-disk-usage-on-azure-vm</link><description>CollectGuestLogs.exe is one of Microsoft Tools that is installed with VM’s stored on Azure. While I’m sure it has many…</description><pubDate>Tue, 26 Jun 2018 19:47:57 GMT</pubDate><guid>https://evotec.xyz/de/blog/collectguestlogs-exe-high-disk-usage-on-azure-vm</guid><category>azure</category><category>Azure AD</category><category>azure vm</category><category>collectguestlogs</category><category>Windows</category></item><item><title>Office 365 – onmicrosoft.com address missing from user synchronized from Active Directory</title><link>https://evotec.xyz/de/blog/office-365-onmicrosoft-com-address-missing-user-synchronized-active-directory</link><description>Onmicrosoft.com address is standard email address used by Office 365. While usually Clients tend to use their own domains onmicrosoft.com…</description><pubDate>Wed, 17 Jan 2018 22:31:02 GMT</pubDate><guid>https://evotec.xyz/de/blog/office-365-onmicrosoft-com-address-missing-user-synchronized-active-directory</guid><category>Active Directory</category><category>Azure AD</category><category>exchange</category><category>exchange 2013</category><category>exchange online</category><category>exchange target address</category><category>microsoft office 365</category><category>Office 365</category><category>office365</category><category>onmicrosoft.com</category></item><item><title>Azure ADConnect Export Failed – Permission-issue error</title><link>https://evotec.xyz/de/blog/azure-adconnect-export-failed-permission-issue-error</link><description>During our recent setup of Azure ADConnect for one of our Clients we’ve been getting permission-issue – Insufficient access rights…</description><pubDate>Sun, 08 Oct 2017 19:23:20 GMT</pubDate><guid>https://evotec.xyz/de/blog/azure-adconnect-export-failed-permission-issue-error</guid><category>active directory</category><category>adconnect</category><category>azure ad</category><category>azure adconnect</category><category>error</category><category>errors</category><category>export failed</category><category>office 365</category><category>permission-issue</category><category>permissions</category><category>powershell</category><category>windows 2012R2</category><category>windows 2016</category><category>windows server 2016</category></item></channel></rss>