{"id":69,"title":"Microsoft 365 ve Active Directory E\u015fitleme Sorunlar\u0131nda Kontrol Edilmesi Gerekenler","content":"

Azure AD Connect (ADConnect) kullanarak Active Directory (AD) ile Microsoft 365 aras\u0131nda senkronizasyon yap\u0131yorsan\u0131z, bazen kullan\u0131c\u0131lar\u0131n beklendi\u011fi gibi e\u015fitlenmedi\u011fini görebilirsiniz.<\/p>\r\n

\"ADConnect çal\u0131\u015f\u0131yor, senkronizasyon komutu ba\u015far\u0131l\u0131 oldu, ancak kullan\u0131c\u0131 Microsoft 365'te görünmüyor!\"<\/strong><\/p>\r\n

Peki, bu durumda neleri kontrol etmelisiniz? \u0130\u015fte ad\u0131m ad\u0131m incelemeniz gerekenler:<\/p>\r\n

1\ufe0f\u20e3 Kullan\u0131c\u0131 Do\u011fru OU (Organizational Unit) \u0130çinde mi?<\/strong><\/h2>\r\n

ADConnect, yaln\u0131zca belirlenen OU’lardaki kullan\u0131c\u0131lar\u0131 e\u015fitler. Kullan\u0131c\u0131 yanl\u0131\u015f OU’da ise senkronizasyon d\u0131\u015f\u0131nda kal\u0131r.<\/p>\r\n

\u2714 Kontrol:<\/strong><\/p>\r\n

    \r\n
  • \r\n

    ADConnect Yönetici Konsolu<\/strong> → \"Synchronization Rules\"<\/strong> → \"Organizational Unit Selection\"<\/strong><\/p>\r\n<\/li>\r\n

  • \r\n

    PowerShell:<\/strong> Get-ADSyncConnector | Select-Object Name, Partition<\/code><\/p>\r\n<\/li>\r\n<\/ul>\r\n

    2\ufe0f\u20e3 UPN (User Principal Name) Format\u0131 Do\u011fru mu?<\/strong><\/h2>\r\n

    Kullan\u0131c\u0131n\u0131n UPN’si (user@firmaadi.com<\/code>), Microsoft 365’teki do\u011frulanm\u0131\u015f domain ile ayn\u0131 olmal\u0131d\u0131r.<\/p>\r\n

    \u2714 Kontrol:<\/strong><\/p>\r\n

      \r\n
    • \r\n

      AD Kullan\u0131c\u0131 Özellikleri<\/strong> → \"Account\"<\/strong> sekmesi → UPN soneki do\u011fru domain mi?<\/strong><\/p>\r\n<\/li>\r\n

    • \r\n

      PowerShell:<\/strong> Get-ADUser -Identity Kullan\u0131c\u0131Ad\u0131 -Properties UserPrincipalName<\/code><\/p>\r\n<\/li>\r\n<\/ul>\r\n

      \r\n

      Önemli:<\/strong> E\u011fer UPN yanl\u0131\u015fsa, kullan\u0131c\u0131 Azure AD’ye e\u015fitlenmez veya farkl\u0131 bir isimle görünebilir.<\/p>\r\n<\/blockquote>\r\n

      3\ufe0f\u20e3 ProxyAddress (E-posta Adresleri) Tan\u0131ml\u0131 m\u0131?<\/strong><\/h2>\r\n

      Exchange Online’da kullan\u0131c\u0131 olu\u015fabilmesi için proxyAddresses<\/code> özniteli\u011finde SMTP adresleri tan\u0131ml\u0131 olmal\u0131d\u0131r.<\/p>\r\n

      \u2714 Kontrol:<\/strong><\/p>\r\n

        \r\n
      • \r\n

        AD Users and Computers<\/strong> → \"Attribute Editor\"<\/strong> → \"proxyAddresses\"<\/strong> alan\u0131<\/p>\r\n<\/li>\r\n

      • \r\n

        PowerShell:<\/strong> Get-ADUser -Identity Kullan\u0131c\u0131Ad\u0131 -Properties proxyAddresses<\/code><\/p>\r\n<\/li>\r\n<\/ul>\r\n

        \r\n

        Dikkat:<\/strong> Birincil e-posta (SMTP:user@firmaadi.com<\/code>) büyük harfle yaz\u0131lmal\u0131, di\u011fer alternatif e-postalar küçük harfle (smtp:user@eski-firma.com<\/code>) belirtilmelidir.<\/p>\r\n<\/blockquote>\r\n

        4\ufe0f\u20e3 Kullan\u0131c\u0131 Devre D\u0131\u015f\u0131 (Disabled) Durumda m\u0131?<\/strong><\/h2>\r\n
          \r\n
        • \r\n

          AD’de \"Account disabled\"<\/strong> olan kullan\u0131c\u0131lar varsay\u0131lan olarak e\u015fitlenmez.<\/p>\r\n<\/li>\r\n

        • \r\n

          Baz\u0131 GPO’lar veya script’ler kullan\u0131c\u0131y\u0131 senkronizasyon d\u0131\u015f\u0131nda b\u0131rakabilir.<\/p>\r\n<\/li>\r\n<\/ul>\r\n

          \u2714 Kontrol:<\/strong><\/p>\r\n

            \r\n
          • \r\n

            AD Users and Computers<\/strong> → Kullan\u0131c\u0131 özellikleri → \"Account is disabled\"<\/strong><\/p>\r\n<\/li>\r\n

          • \r\n

            PowerShell:<\/strong> Get-ADUser -Identity Kullan\u0131c\u0131Ad\u0131 -Properties Enabled<\/code><\/p>\r\n<\/li>\r\n<\/ul>\r\n

            5\ufe0f\u20e3 Azure AD Connect Servisi Çal\u0131\u015f\u0131yor mu?<\/strong><\/h2>\r\n

            Bazen Start-ADSyncSyncCycle -PolicyType Delta<\/code> komutu çal\u0131\u015fsa bile arka planda senkronizasyon servisi durmu\u015f olabilir.<\/p>\r\n

            \u2714 Kontrol:<\/strong><\/p>\r\n

              \r\n
            • \r\n

              Services.msc<\/strong> → \"Microsoft Azure AD Sync\"<\/strong> servisinin \"Running\"<\/strong> durumda oldu\u011funu do\u011frulay\u0131n.<\/p>\r\n<\/li>\r\n

            • \r\n

              Event Viewer<\/strong> → Applications and Services Logs<\/strong> → Azure AD Sync<\/strong> hatalar\u0131n\u0131 inceleyin.<\/p>\r\n<\/li>\r\n<\/ul>\r\n

              \ud83d\udca1 Ek Kontroller:<\/strong><\/h2>\r\n
                \r\n
              • \r\n

                E\u015fitleme Profilini Do\u011frulay\u0131n:<\/strong><\/p>\r\n

                  \r\n
                • \r\n

                  \"Staging Mode\"<\/strong> aktif mi? (Staging modda de\u011fi\u015fiklikler test edilir ancak Azure AD’ye aktar\u0131lmaz.)<\/p>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n

                • \r\n

                  Filtreleme Kurallar\u0131n\u0131 Kontrol Edin:<\/strong><\/p>\r\n

                    \r\n
                  • \r\n

                    \"Scope Filtering\"<\/strong> ayarlar\u0131 kullan\u0131c\u0131y\u0131 engelliyor olabilir.<\/p>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n

                  • \r\n

                    Azure AD Connect Upgrade Gerekli mi?<\/strong><\/p>\r\n

                      \r\n
                    • \r\n

                      Eski bir sürüm kullan\u0131yorsan\u0131z, güncelleme yap\u0131n.<\/p>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n

                      \ud83d\udd27 Sorun Giderme Ad\u0131mlar\u0131:<\/strong><\/h2>\r\n
                        \r\n
                      1. \r\n

                        Delta Sync Ba\u015flat:<\/strong><\/p>\r\n

                        \r\n
                        \r\n
                        \r\n
                        \r\n
                        \r\n
                        \r\n
                        \r\n
                        \r\n
                        \r\n
                        Start-ADSyncSyncCycle -PolicyType Delta<\/pre>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n
                         <\/pre>\r\n<\/div>\r\n<\/li>\r\n
                      2. \r\n
                        Tam Senkronizasyon Zorla (Gerekirse):<\/strong><\/p>\r\n
                        \r\n
                        \r\n
                        \r\n
                        \r\n
                         <\/div>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n
                        Start-ADSyncSyncCycle -PolicyType Initial<\/pre>\r\n <\/div>\r\n<\/li>\r\n
                      3. \r\n
                        Azure AD Connect Health ile Sorunlar\u0131 \u0130zle:<\/strong><\/p>\r\n
                        Azure Portal → Azure AD Connect Health<\/pre>\r\n <\/li>\r\n<\/ol>\r\n
                        Active Directory ve Microsoft 365 e\u015fitleme sorunlar\u0131n\u0131 çözmek için OU seçimi, UPN, proxyAddress, kullan\u0131c\u0131 durumu ve ADConnect servis durumu<\/strong> en kritik noktalard\u0131r. Bu ad\u0131mlar\u0131 kontrol ederek sorunun kayna\u011f\u0131n\u0131 h\u0131zl\u0131ca tespit edebilirsiniz.<\/p>\r\n
                        E\u011fer hala sorun devam ediyorsa, Azure AD Connect Synchronization Service Manager<\/strong> üzerinden detayl\u0131 hata loglar\u0131n\u0131 inceleyebilirsiniz.<\/p>\r\n
                        #AzureAD #ActiveDirectory #Microsoft365 #ADConnect #SenkronizasyonSorunlar\u0131<\/strong><\/p>","excerpt":"Azure AD Connect (ADConnect) kullanarak Active Directory (AD) ile Microsoft 365 aras\u0131nda senkronizasyon yap\u0131yorsan\u0131z, bazen kullan\u0131c\u0131lar\u0131n...","created_at":"2025-05-03 10:52:42","updated_at":"2026-09-06 18:57:14","category_id":8,"view_count":860,"reading_time":3,"status":"published","editor_choice":0,"is_editor_choice":0,"published_at":"2025-05-03 10:52:42","featured_image":"resimyok.jpg","slug":"microsoft-365-adconnect","category_name":"Active Directory \/Azure","category_slug":"active-directory-azure"}