Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MSFT_EXOOrganizationConfig] does not implement the write property SendFromEmailAliasEnabled #1689

Closed
SebastianGoers opened this issue Jan 19, 2022 · 1 comment · Fixed by #1694 or #1696
Assignees

Comments

@SebastianGoers
Copy link

Details of the scenario you tried and the problem that is occurring

Test-TargetResource of the PS module MSFT_EXOOrganizationConfig does not implement the write property
SendFromEmailAliasEnabled

Verbose logs showing the problem

The command Test-TargetResource of the PS module MSFT_EXOOrganizationConfig does not implement the write property 
SendFromEmailAliasEnabled mentioned in the corresponding MOF schema file C:\Program Files\WindowsPowerShell\Modules\Mic
rosoft365DSC\1.22.119.1\DscResources\MSFT_EXOOrganizationConfig\MSFT_EXOOrganizationConfig.schema.mof. All write 
paramenters mentioned in the schema file must be implemented by the command Test-TargetResource.
    + CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : WriteParameterNotImplemented
    + PSComputerName        : localhost

Suggested solution to the issue

The DSC configuration that is used to reproduce the issue (as detailed as possible)

# insert configuration here

The operating system the target node is running

Version of the DSC module that was used ('dev' if using current dev branch)

1.22.119.1

@SebastianGoers SebastianGoers changed the title [MSFT_EXOOrganizationConfig] does not implement the write property SendFromEmailAliasEnabled mentioned [MSFT_EXOOrganizationConfig] does not implement the write property SendFromEmailAliasEnabled Jan 19, 2022
andikrueger added a commit to andikrueger/Microsoft365DSC that referenced this issue Jan 20, 2022
@andikrueger andikrueger self-assigned this Jan 20, 2022
@andikrueger
Copy link
Collaborator

Good catch. The variable name within the class description did not match the parameter name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment