User Profile
CSU_Scott
Brass Contributor
Joined 8 years ago
User Widgets
Recent Discussions
Prefill Username for Authentication
Good morning, We have a landing page for two different tenants with different domains. For example, xyz.com and other.xyz.com. I want to create logic for a landing page where the user enters their name as mailto:email address removed for privacy reasons and is routed to the authentication for the appropriate tenant. That part is fairly trivial. The user is then presented with a dialog asking for their username and password by the EntraID IDP. Is there a way to prefill the username to eliminate the need to enter the password twice? Best regards, ScottRe: Generating An Empty Global Address List By Default
I like this too. As I read through it, I don't think I can do that. The goal is to not publish the data in the Address Lists by default. They should be allowed to communicate with each other if the users are aware of each other. We want to minimize the publishing of their information while allowing them to communicate as needed. What about setting all of the existing address lists to Null? Anyone aware of ramifications of doing this?Re: Generating An Empty Global Address List By Default
Thank you FcoManigrasso We have gone down that path, but what we need is all users to be automatically without any address book without assigning an address book policy. We need to make an empty address book the default policy so we don't have to assign it via a PowerShell script post launch. Best regards, ScottRe: Generating An Empty Global Address List By Default
We have empty address lists. I don't see a way to set the address book policy as the default despite get-addressbookpolicy having a setting for IsDefault. I don't get an option in set-addressbookpolicy to make it the default address book policy in Exchange Online. Best regards, ScottGenerating An Empty Global Address List By Default
Good afternoon, Is it possible to generate or update Exchange Online's default address lists for all users in a tenant to be completely empty without generating new lists and address books and assigning them to mailboxes? We are looking for a method to automatically provide empty address lists to all users across the board without setting the user's mailbox to hidden from GAL or assigning an address book policy. Best regards, CSU_ScottFormatting All Columns in Microsoft or Sharepoint Lists
I wanted a generic way to apply formatting to all columns of a list without going column by column and editing each. Currently, I am doing that but substituted the field name for @currentField. This works, but does generate an error. { "$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json", "elmType": "div", "style": { "box-sizing": "border-box", "padding": "0 2px", "overflow": "hidden", "text-overflow": "ellipsis" }, "attributes": { "class": { "operator": ":", "operands": [ { "operator": "==", "operands": [ "@currentField", "Working Remote" ] }, "sp-css-backgroundColor-BgMintGreen sp-css-borderColor-MintGreenFont sp-css-color-MintGreenFont sp-field-bold", { "operator": ":", "operands": [ { "operator": "==", "operands": [ "@currentField", "Vacation Unavailable" ] }, "sp-css-backgroundColor-BgDustRose sp-css-borderColor-DustRoseFont sp-css-color-DustRoseFont sp-field-bold", { "operator": ":", "operands": [ { "operator": "==", "operands": [ "@currentField", "Vacation Available" ] }, "sp-css-backgroundColor-BgGold sp-css-borderColor-GoldFont sp-css-color-GoldFont sp-field-bold", { "operator": ":", "operands": [ { "operator": "==", "operands": [ "@currentField", "Working Campus" ] }, "sp-css-backgroundColor-BgMintGreen sp-css-borderColor-MintGreenFont sp-field-fontSizeSmall sp-css-color-MintGreenFont sp-field-bold", "" ] } ] } ] } ] } }, "txtContent": "@currentField" } Saving the column format generates the following error, which I am not sure is detrimental as the formatting does work as expected. I think the Id variable at the end is blank and kicks off the error. {"d": {"CustomFormatter": "{\"$schema\":\"https:\u002F\u002Fdeveloper.microsoft.com\u002Fjson-schemas\u002Fsp\u002Fv2\u002Fcolumn-formatting.schema.json\",\"elmType\":\"div\",\"style\":{\"box-sizing\":\"border-box\",\"padding\":\"0 2px\",\"overflow\":\"hidden\",\"text-overflow\":\"ellipsis\"},\"attributes\":{\"class\":{\"operator\":\":\",\"operands\":[{\"operator\":\"==\",\"operands\":[\"@currentField\",\"Working Remote\"]},\"sp-css-backgroundColor-BgMintGreen sp-css-borderColor-MintGreenFont sp-css-color-MintGreenFont sp-field-bold\",{\"operator\":\":\",\"operands\":[{\"operator\":\"==\",\"operands\":[\"@currentField\",\"Vacation Unavailable\"]},\"sp-css-backgroundColor-BgDustRose sp-css-borderColor-DustRoseFont sp-css-color-DustRoseFont sp-field-bold\",{\"operator\":\":\",\"operands\":[{\"operator\":\"==\",\"operands\":[\"@currentField\",\"Vacation Available\"]},\"sp-css-backgroundColor-BgGold sp-css-borderColor-GoldFont sp-css-color-GoldFont sp-field-bold\",{\"operator\":\":\",\"operands\":[{\"operator\":\"==\",\"operands\":[\"@currentField\",\"Working Campus\"]},\"sp-css-backgroundColor-BgMintGreen sp-css-borderColor-MintGreenFont sp-field-fontSizeSmall sp-css-color-MintGreenFont sp-field-bold\",\"\"]}]}]}]}},\"txtContent\":\"@currentField\"}", "Id": ""}} 1. Is there a way to apply this type of formatting to the entire list so that all columns are formatter? 2. Is there a way to correct my JSON formatting as to not generate the error? Can I form it more properly? Thanks in advance. CSU_Scott New List and SharePoint user/admin.Azure AD Connect Failed Automatic Upgrade 1.6.16.0 to 2.1.16.0
We had an automatic upgrade fail for our Azure AD Connect from version 1.6.16.0 to 2.1.16.0. logs show the following: Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::SetStringValue(HKEY_LOCAL_MACHINE, SYSTEM\CurrentControlSet\services\ADSync\Parameters, SqlAoaAsyncMode, False) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::SetStringValue Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::SetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, ServiceAccountType, VirtualServiceAccount) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::SetStringValue Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, GroupAdmins, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:ADSyncAdmins Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, GroupOperators, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:ADSyncOperators Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, GroupBrowse, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:ADSyncBrowse Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, GroupPasswordSet, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:ADSyncPasswordSet Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SYSTEM\CurrentControlSet\services\ADSync\Parameters, Path, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:C:\Program Files\Microsoft Azure AD Sync\ Azure AD Connect Upgrade Information: 904 : SynchronizationServiceSetupTask: UpgradeCore: Attempting to upgrade LocalDB instance. Azure AD Connect Upgrade Information: 904 : SyncServiceAccount: Using a VirtualServiceAccount Azure AD Connect Upgrade Information: 402 : SyncServiceAccount:ResolveSid path=WinNT://NT SERVICE/ADSync Azure AD Connect Upgrade Verbose: 903 : Found sid SidTypeWellKnownGroup : S-1-5-80-3245704983-3664226991-764670653-2504430226-901976451 Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::DoesRegistrySubKeyExist(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileListS-1-5-80-3245704983-3664226991-764670653-2504430226-901976451.bak) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::DoesRegistrySubKeyExist:False Azure AD Connect Upgrade Information: 904 : SyncServiceAccount.ResolveSid: SyncServiceAccount.SidString=S-1-5-80-3245704983-3664226991-764670653-2504430226-901976451 Azure AD Connect Upgrade Verbose: 903 : IsMemberOfLocalGroup: Encountered error when enumerating group member. Details: The user name or password is incorrect. Azure AD Connect Upgrade Verbose: 903 : IsMemberOfLocalGroup: Encountered error when enumerating group member. Details: The user name or password is incorrect. Azure AD Connect Upgrade Verbose: 903 : IsMemberOfLocalGroup: (it loops at this point until you kill the upgrade process if running manually) On a healthy install, it looks like this -- bolding the area where this successfully seemed to install in the healthy sync environment. Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::SetStringValue(HKEY_LOCAL_MACHINE, SYSTEM\CurrentControlSet\services\ADSync\Parameters, SqlAoaAsyncMode, False) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::SetStringValue Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::SetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, ServiceAccountType, VirtualServiceAccount) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::SetStringValue Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, GroupAdmins, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:ADSyncAdmins Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, GroupOperators, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:ADSyncOperators Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, GroupBrowse, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:ADSyncBrowse Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion, GroupPasswordSet, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:ADSyncPasswordSet Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::GetStringValue(HKEY_LOCAL_MACHINE, SYSTEM\CurrentControlSet\services\ADSync\Parameters, Path, {NULL}) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::GetStringValue:C:\Program Files\Microsoft Azure AD Sync\ Azure AD Connect Upgrade Information: 904 : SynchronizationServiceSetupTask: UpgradeCore: Attempting to upgrade LocalDB instance. Azure AD Connect Upgrade Information: 904 : SyncServiceAccount: Using a VirtualServiceAccount Azure AD Connect Upgrade Information: 402 : SyncServiceAccount:ResolveSid path=WinNT://NT SERVICE/ADSync Azure AD Connect Upgrade Verbose: 903 : Found sid SidTypeWellKnownGroup : S-1-5-80-3245704983-3664226991-764670653-2504430226-901976451 Azure AD Connect Upgrade Verbose: 901 : >>> RegistryAdapter::DoesRegistrySubKeyExist(HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileListS-1-5-80-3245704983-3664226991-764670653-2504430226-901976451.bak) Azure AD Connect Upgrade Verbose: 902 : <<< RegistryAdapter::DoesRegistrySubKeyExist:False Azure AD Connect Upgrade Information: 904 : SyncServiceAccount.ResolveSid: SyncServiceAccount.SidString=S-1-5-80-3245704983-3664226991-764670653-2504430226-901976451 Azure AD Connect Upgrade Information: 904 : SyncServiceAccount:AddToLocalAdministratorsGroup: Azure AD Connect Upgrade Information: 904 : Starting: Temporarily adding the ADSync account to the local Administrators group... Azure AD Connect Upgrade Verbose: 903 : The 'WinNT://NT SERVICE/ADSync' has been added to the 'WinNT://SYNC-AAD-01A/Administrators,group' successfully. Azure AD Connect Upgrade Information: 904 : Finished: Temporarily adding the ADSync account to the local Administrators group. Duration: 0.013 sec. Azure AD Connect Upgrade Verbose: 903 : RestartBootstrapService: [22:17:16.308] [ 1] [INFO ] ServiceControllerProvider: processing StopService request for: ADSync [22:17:16.308] [ 1] [VERB ] ServiceControllerProvider: Initial service status: Running [22:17:16.308] [ 1] [VERB ] ServiceControllerProvider: stopping service and waiting for completion. [22:17:34.264] [ 1] [INFO ] ServiceControllerProvider: StopService status: Stopped [22:17:34.264] [ 1] [INFO ] ServiceControllerProvider: Processing StartService request for: ADSync [22:17:34.264] [ 1] [VERB ] ServiceControllerProvider: Initial service status: Stopped [22:17:34.264] [ 1] [VERB ] ServiceControllerProvider: Starting service and waiting for completion. [22:17:34.717] [ 1] [INFO ] ServiceControllerProvider: StartService status: Running Azure AD Connect Upgrade Verbose: 903 : RestartBootstrapService: completed successfully. Azure AD Connect Upgrade Information: 904 : SynchronizationServiceSetupTask: UpgradeCore: Upgraded LocalDB instance successfully created. Azure AD Connect Upgrade Verbose: 903 : RestartBootstrapService: [22:18:02.480] [ 1] [INFO ] ServiceControllerProvider: processing StopService request for: ADSync [22:18:02.480] [ 1] [VERB ] ServiceControllerProvider: Initial service status: Running Any thoughts on what I should be looking for here? We opened a ticket on the 15th and I feel like we are just spinning our wheels at this point. Hoping someone from the community may have seen this issue previously. Best regards, ScottTenant to Tenant Send and Receive Connectors
We have two tenants TenantA and TenantB. There is a third party filtering service in front of both and routes Internet email to the appropriate tenant after filtering. We want to create a direct connection between the tenants. If I create a connector for TenantA from O365 to Partner Organization's Smart Host TenantB.mail.protection.outlook.com, that seems like it could work. On the TenantB side, we have a receive connector that is locked down to only receive mail from the third party filtering service and their range of IP's. I could allow EOP's IP ranges, but that seems like it could be abused. Anyone implement direct connectors between tenants for email exchange involving smart hosts instead of MX records? Best regards, Scott
